From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/3] avformat/imfdec: remove the experimental flag
Date: Mon, 20 Feb 2023 11:34:17 -0800
Message-ID: <CAF_7JxA0s8=Kk8dBk8Zd+oTQjOraR4bzq+CJbfNHusm0ZMw5jA@mail.gmail.com> (raw)
In-Reply-To: <167691570385.10789.9819994676341301664@lain.khirnov.net>
On Mon, Feb 20, 2023 at 9:55 AM Anton Khirnov <anton@khirnov.net> wrote:
>
> Quoting pal@sandflow.com (2023-01-06 00:29:44)
> > From: Pierre-Anthony Lemieux <pal@palemieux.com>
> >
> > ---
> > libavformat/imfdec.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavformat/imfdec.c b/libavformat/imfdec.c
> > index 03de9ce151..a92686e93b 100644
> > --- a/libavformat/imfdec.c
> > +++ b/libavformat/imfdec.c
> > @@ -1018,7 +1018,7 @@ static const AVClass imf_class = {
> > const AVInputFormat ff_imf_demuxer = {
> > .name = "imf",
> > .long_name = NULL_IF_CONFIG_SMALL("IMF (Interoperable Master Format)"),
> > - .flags = AVFMT_EXPERIMENTAL | AVFMT_NO_BYTE_SEEK,
> > + .flags = AVFMT_NO_BYTE_SEEK,
>
> The demuxer has been upstream for quite a while without too many issues,
> so I'd say this is reasonable.
Ok. Will apply tomorrow unless objections are raised.
>
> --
> Anton Khirnov
_______________________________________________
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".
prev parent reply other threads:[~2023-02-20 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 23:29 pal
2023-01-05 23:29 ` [FFmpeg-devel] [PATCH v2 2/3] doc: improve IMF demuxer documentation pal
2023-01-05 23:29 ` [FFmpeg-devel] [PATCH v2 3/3] fate/imfdec: remove imf experimental flag pal
2023-01-06 15:45 ` [FFmpeg-devel] [PATCH v2 1/3] avformat/imfdec: remove the " Tomas Härdin
2023-01-06 15:50 ` Pierre-Anthony Lemieux
2023-01-06 16:09 ` Tomas Härdin
2023-01-06 16:18 ` Pierre-Anthony Lemieux
2023-02-20 17:55 ` Anton Khirnov
2023-02-20 19:34 ` Pierre-Anthony Lemieux [this message]
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='CAF_7JxA0s8=Kk8dBk8Zd+oTQjOraR4bzq+CJbfNHusm0ZMw5jA@mail.gmail.com' \
--to=pal@sandflow.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