From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] 5.0 blocking issues
Date: Mon, 10 Jan 2022 18:32:22 +0800
Message-ID: <tencent_EFC84DD3EDF36A95C4E9138EA6C54A930405@qq.com> (raw)
In-Reply-To: <tencent_73A1570F9D4EE04E5BA83449804034E73F09@qq.com>
> > A regression issue: avformat/movenc: fix duration in mdhd box
> > https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_7D4D80DC34DB3F53572F9D76E0EE5AEE3509@qq.com/
>
> https://patchwork.ffmpeg.org/check/48152/
>
> Make fate failed?
> make: *** [fate-copy-trac3074] Error 1
> make: *** [fate-mov-mp4-disposition-mpegts-remux] Error 1
> make: *** [fate-mov-cover-image] Error 1
Fixed by v4 which doesn’t reached patchwork yet.
https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_C134573E6B56A39D92E0345A0634B9814E09@qq.com/
There are a lot of false positive reports, better be cleanly up afterwards.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-01-10 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 16:30 Michael Niedermayer
2022-01-08 16:36 ` Romain Beauxis
2022-01-08 18:55 ` Soft Works
2022-01-08 21:31 ` Lynne
2022-01-10 3:09 ` "zhilizhao(赵志立)"
2022-01-10 9:04 ` lance.lmwang
2022-01-10 10:32 ` "zhilizhao(赵志立)" [this message]
2022-01-10 16:55 ` Anton Khirnov
2022-01-10 18:12 ` Andreas Rheinhardt
2022-01-12 6:37 ` Lynne
2022-01-12 16:30 ` Michael Niedermayer
2022-01-12 16:36 ` Nicolas George
2022-01-12 16:41 ` James Almer
2022-01-12 16:47 ` Nicolas George
2022-01-12 17:30 ` Jean-Baptiste Kempf
2022-01-12 17:58 ` Nicolas George
2022-01-12 23:17 ` Michael Niedermayer
2022-01-12 21:35 ` Soft Works
2022-01-13 4:02 ` Xiang, Haihao
2022-01-13 11:34 ` James Almer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_EFC84DD3EDF36A95C4E9138EA6C54A930405@qq.com \
--to=quinkblack@foxmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git