From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] SDR lib comments
Date: Fri, 29 Sep 2023 09:03:13 +0200
Message-ID: <ZRZ2scY18TXeoA0W@phare.normalesup.org> (raw)
In-Reply-To: <A5342223-2251-434C-891B-2D5A88E8845B@remlab.net>
Rémi Denis-Courmont (12023-09-29):
> And as a downstream OSS application developer, I'd really rather
> postproc be officially and properly dropped, so I can justify dropping
> it downstream as well.
Let me get this straight? You COULD just add --disable-postproc in your
downstream project and be done with it, but you would rather that FFmpeg
removes the feature (granted, of limited use, but still of use to some
people) so that you do not take the blame for removing it?
Well, I think this makes it obvious why I think people representing
downstream projects should have very little influence on the future of
FFmpeg.
--
Nicolas George
_______________________________________________
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:[~2023-09-29 7:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:43 Michael Niedermayer
2023-09-28 10:28 ` Anton Khirnov
2023-09-28 19:28 ` Michael Niedermayer
2023-09-28 21:05 ` Rémi Denis-Courmont
2023-09-28 22:18 ` Michael Niedermayer
2023-09-29 7:03 ` Nicolas George [this message]
2023-09-29 8:23 ` Rémi Denis-Courmont
2023-10-02 10:08 ` Nicolas George
2023-09-29 8:34 ` Rémi Denis-Courmont
2023-10-02 10:06 ` Nicolas George
2023-09-29 12:59 ` Vittorio Giovara
2023-10-02 10:05 ` Nicolas George
2023-09-28 21:07 ` Vittorio Giovara
2023-09-28 22:58 ` Michael Niedermayer
2023-09-29 9:43 ` Anton Khirnov
2023-09-29 11:43 ` Nicolas George
2023-09-29 13:29 ` Rémi Denis-Courmont
2023-09-29 13:53 ` Nicolas George
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=ZRZ2scY18TXeoA0W@phare.normalesup.org \
--to=george@nsup.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