From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: "marth64@proxyid.net" <marth64@proxyid.net>
Subject: Re: [FFmpeg-devel] [PATCH] rcwtenc: add sub-rcwt fate test ref
Date: Mon, 15 Jan 2024 05:06:26 +0000
Message-ID: <bfea48cbb7f1a4e80d675481c0f84b26013285fc.camel@intel.com> (raw)
In-Reply-To: <20240115043805.76904-1-marth64@proxyid.net>
On So, 2024-01-14 at 22:38 -0600, Marth64 wrote:
> Resolves the issue. Patch generated with git format-patch and validated to
> apply.
> I reget any inconvenience this may have caused. Respectfully,
>
> Signed-off-by: Marth64 <marth64@proxyid.net>
> ---
> tests/ref/fate/sub-rcwt | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 tests/ref/fate/sub-rcwt
>
> diff --git a/tests/ref/fate/sub-rcwt b/tests/ref/fate/sub-rcwt
> new file mode 100644
> index 0000000000..722cbe1c5b
> --- /dev/null
> +++ b/tests/ref/fate/sub-rcwt
> @@ -0,0 +1 @@
> +d86f179094a5752d68aa97d82cf887b0
Thanks for your quick fix, it works well for me.
BRs
Haihao
_______________________________________________
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:[~2024-01-15 5:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 2:14 [FFmpeg-devel] [PATCH] libavformat: add RCWT closed caption muxer Marth64
2024-01-06 12:33 ` Stefano Sabatini
2024-01-06 21:41 ` [FFmpeg-devel] [PATCH v2] " Marth64
2024-01-07 12:02 ` Stefano Sabatini
2024-01-07 15:07 ` [FFmpeg-devel] [PATCH v3] " Marth64
2024-01-07 15:24 ` Stefano Sabatini
2024-01-14 14:16 ` Stefano Sabatini
2024-01-14 16:57 ` Marth64
2024-01-15 4:25 ` Xiang, Haihao
2024-01-15 4:33 ` Marth64
2024-01-15 4:38 ` [FFmpeg-devel] [PATCH] rcwtenc: add sub-rcwt fate test ref Marth64
2024-01-15 5:06 ` Xiang, Haihao [this message]
2024-01-15 5:20 ` Marth64
2024-01-15 23:55 ` Marth64
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=bfea48cbb7f1a4e80d675481c0f84b26013285fc.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=marth64@proxyid.net \
/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