From: Muhammad Faiz <mfcc64@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/fifo: Remove (a)fifo filters
Date: Sat, 9 Mar 2024 07:38:13 +0700
Message-ID: <CAJsO9v6PVP3W9WE3=pchPpUZmqKDk3Gs95Kbg_fUNa-cQJGroQ@mail.gmail.com> (raw)
In-Reply-To: <GV1SPRMB005293A609FAEDBA48B40B2E8F272@GV1SPRMB0052.EURP250.PROD.OUTLOOK.COM>
On Fri, Mar 8, 2024 at 10:46 PM Andreas Rheinhardt <
andreas.rheinhardt@outlook.com> wrote:
> Muhammad Faiz:
> > On Fri, Mar 8, 2024 at 5:40 PM Andreas Rheinhardt <
> > andreas.rheinhardt@outlook.com> wrote:
> >
> >> Muhammad Faiz:
> >>> On Tue, Feb 6, 2024 at 3:58 PM Andreas Rheinhardt <
> >>> andreas.rheinhardt@outlook.com> wrote:
> >>>
> >>>> Andreas Rheinhardt:
> >>>>> Obsolete since 4ca1fb9d2a91757c8c4c34dd456abf340e3f765f.
> >>>>>
> >>>>> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> >>>>> ---
> >>>>> doc/filters.texi | 9 ---
> >>>>> libavfilter/Makefile | 1 -
> >>>>> libavfilter/allfilters.c | 2 -
> >>>>> libavfilter/fifo.c | 165
> ---------------------------------------
> >>>>> 4 files changed, 177 deletions(-)
> >>>>> delete mode 100644 libavfilter/fifo.c
> >>>>>
> >>>>
> >>>> Will apply in a few days unless there are objections.
> >>>>
> >>>> - Andreas
> >>>>
> >>>>
> >>> This breaks backward compatibility.
> >>>
> >>> Please revert.
> >>>
> >>> Thank's.
> >>
> >> What breaks that can't simply be fixed by removing the (a)fifo filter
> >> from the filterchain?
> >>
> >> - Andreas
> >>
> >>
> > I use afifo to optimize memory usage.
> > And backward incompatible change should only be allowed with deprecation
> > periods and major version bump.
> >
>
> Deprecation periods etc. are only common for API breaks; we do not
> guarantee that any particular filter etc. stays available and therefore
> occasionally remove them without deprecation. Examples of this are the
> removal of libopenjpeg in 60ccb3fe787, the removal of libwavpackenc in
> 45070eec4c or the removal of the XvMC hardware acceleration in
> be95df12bb06 (the last commit was accompanied by cefa595361db9 and
> b648ece34b6f which deprecated the parts of XvMC that were part of the
> public API and therefore subject to the API stability contract).
>
> - Andreas
>
>
It seems that all of them are external dependent components. So, I think
that non external dependent components should be treated differently.
Also, what is the urgency of (a)fifo removal?
Thank's
_______________________________________________
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-03-09 0:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 13:51 Andreas Rheinhardt
2024-02-06 9:00 ` Andreas Rheinhardt
2024-03-08 8:46 ` Muhammad Faiz
2024-03-08 10:40 ` Andreas Rheinhardt
2024-03-08 15:18 ` Muhammad Faiz
2024-03-08 15:29 ` Paul B Mahol
2024-03-09 1:08 ` Muhammad Faiz
2024-03-09 11:10 ` Paul B Mahol
2024-03-09 22:37 ` Muhammad Faiz
2024-03-08 15:31 ` Andreas Rheinhardt
2024-03-09 0:38 ` Muhammad Faiz [this message]
2024-03-09 11:59 ` Andreas Rheinhardt
2024-03-09 22:36 ` Muhammad Faiz
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='CAJsO9v6PVP3W9WE3=pchPpUZmqKDk3Gs95Kbg_fUNa-cQJGroQ@mail.gmail.com' \
--to=mfcc64@gmail.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