From: Philip Langdale <philipl@overt.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/3] libswscale: add support for VUYX format
Date: Fri, 19 Aug 2022 19:15:04 -0700
Message-ID: <20220819191504.33a38f17@fido7> (raw)
In-Reply-To: <3570ad2f-1c59-3289-4767-ccab6d121646@gmail.com>
On Fri, 19 Aug 2022 22:37:00 -0300
James Almer <jamrial@gmail.com> wrote:
> > diff --git a/tests/ref/fate/pixfmt_best b/tests/ref/fate/pixfmt_best
> > index 1da1846275..783c5fe640 100644
> > --- a/tests/ref/fate/pixfmt_best
> > +++ b/tests/ref/fate/pixfmt_best
> > @@ -1 +1 @@
> > -74 tests passed, 0 tests failed.
> > +75 tests passed, 0 tests failed.
>
> Shouldn't this be in patch 1/3?
Indeed. Fixed in v2. Thanks!
--phil
_______________________________________________
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-08-20 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 1:24 [FFmpeg-devel] [PATCH 0/3] vaapi: switch 8bit 444 format to VUYX Philip Langdale
2022-08-20 1:24 ` [FFmpeg-devel] [PATCH 1/3] lavu/pixfmt: Introduce VUYX format Philip Langdale
2022-08-20 1:24 ` [FFmpeg-devel] [PATCH 2/3] libswscale: add support for " Philip Langdale
2022-08-20 1:37 ` James Almer
2022-08-20 2:15 ` Philip Langdale [this message]
2022-08-20 1:24 ` [FFmpeg-devel] [PATCH 3/3] lavc/vaapi: Switch preferred 8bit 444 format to VUYX Philip Langdale
2022-08-20 2:14 [FFmpeg-devel] [PATCH 0/3] v2: vaapi: switch " Philip Langdale
2022-08-20 2:14 ` [FFmpeg-devel] [PATCH 2/3] libswscale: add support for VUYX format Philip Langdale
2022-08-20 4:31 [FFmpeg-devel] [PATCH 0/3] v2: vaapi: switch 8bit 444 format to VUYX Philip Langdale
2022-08-20 4:31 ` [FFmpeg-devel] [PATCH 2/3] libswscale: add support for VUYX format Philip Langdale
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=20220819191504.33a38f17@fido7 \
--to=philipl@overt.org \
--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