From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Date: Thu, 21 Sep 2023 21:44:37 +0200 Message-ID: <CAPYw7P7X5NQgWgH7ONxDwdYQK173FR6VFB6242EYTr4P9jQ8vw@mail.gmail.com> (raw) In-Reply-To: <ZQybZRUSGGlD+lyT@phare.normalesup.org> On Thu, Sep 21, 2023 at 9:37 PM Nicolas George <george@nsup.org> wrote: > Vittorio Giovara (12023-09-21): > > So this is an example of accusatory tone - discrediting the previous > author > > in order to make your arguments have more weight. It's a bad move and > > easily spottable, you should argue with better elements at your disposal, > > not by claiming that I don't package software or don't contribute to > > libavfilter. > > You are misunderstanding my point completely, I am not accusing you of > anything, I am merely using you as an example to show how your argument > is flawed. > > I can take myself as an example instead, if you like it better: > > How much did *I* contribute to hardware acceleration? Zero! > > How much did *I* contribute to assembly optimization? Zero! > > How much do *I* intend to contribute to hardware acceleration? Zero! > > But now, however much I would like to, especially in libavfilter, I > refrain from objecting to new features of hardware acceleration. > > Because I can make the difference between the things that benefit me and > the things that are useful to many users and therefore good for the > project. > > FFmpeg is made a of a lot of parts that are often very independent. That > is on purpose: that way, if somebody is not interested in a part, they > can just ignore it and let others work on it. > > And that is exactly what I am asking you to do: > > Just ignore SDR and let Michael work on it. > > SDR costs NOTHING except Michael's time, and Michael's time is his own > to spend. For the rest of us, the grounds for objecting are the same > NOTHING. > SDR API is not trivial and inclusion of it with all its features and components is not trivial inside FFmpeg libraries. > > > opinion on this release still stands: either a release with everything > or a > > release without the contentious piece of code, but not both. It's > confusing > > to the end users, and shows lack of direction of the project. > > On this we agree, making a second release without the feature just some > people object to it would be a waste of Michael's time. > > -- > 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". > _______________________________________________ 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-21 19:45 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-10 22:14 [FFmpeg-devel] FFmpeg release 6.1 Michael Niedermayer 2023-04-10 22:16 ` James Almer 2023-04-11 8:46 ` Neal Gompa 2023-09-19 17:18 ` Niklas Haas 2023-09-19 19:16 ` Michael Niedermayer 2023-09-19 21:58 ` Lynne 2023-09-20 0:38 ` Neal Gompa 2023-09-20 2:24 ` Xiang, Haihao 2023-09-20 17:24 ` Michael Niedermayer 2023-09-20 17:43 ` Kieran Kunhya 2023-09-20 18:10 ` Michael Niedermayer 2023-09-20 22:47 ` Kieran Kunhya 2023-09-21 3:19 ` Jean-Baptiste Kempf 2023-09-21 12:51 ` Michael Niedermayer 2023-09-20 12:47 ` Niklas Haas 2023-09-20 18:00 ` Michael Niedermayer 2023-09-21 11:46 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics 2023-09-21 16:21 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Michael Niedermayer 2023-09-21 16:33 ` Kieran Kunhya via ffmpeg-devel 2023-09-21 17:16 ` Nicolas George 2023-09-21 18:14 ` Vittorio Giovara 2023-09-21 18:19 ` Nicolas George 2023-09-21 18:47 ` Vittorio Giovara 2023-09-21 18:51 ` Nicolas George 2023-09-21 18:54 ` Vittorio Giovara 2023-09-21 19:04 ` Nicolas George 2023-09-21 19:08 ` Paul B Mahol 2023-09-26 18:14 ` Nicolas George 2023-09-21 19:18 ` Vittorio Giovara 2023-09-21 19:37 ` Nicolas George 2023-09-21 19:44 ` Paul B Mahol [this message] 2023-09-21 18:56 ` Michael Niedermayer 2023-09-26 19:59 ` Rémi Denis-Courmont 2023-09-21 16:39 ` Paul B Mahol 2023-09-22 13:55 ` Gijs Peskens 2023-09-22 16:32 ` Michael Niedermayer 2023-09-23 6:49 ` Neal Gompa 2023-09-23 10:55 ` Michael Niedermayer 2023-09-23 23:31 ` Neal Gompa 2023-09-24 9:12 ` Nicolas George 2023-09-24 11:56 ` Paul B Mahol 2023-09-24 12:17 ` Nicolas George 2023-09-24 17:33 ` Paul B Mahol 2023-09-24 17:45 ` [FFmpeg-devel] libavdevice (was: FFmpeg release 6.1 (SDR Plans)) Nicolas George 2023-09-24 17:49 ` Paul B Mahol 2023-09-24 17:54 ` Nicolas George 2023-09-24 18:05 ` Paul B Mahol 2023-09-24 18:09 ` Nicolas George 2023-09-25 11:20 ` Paul B Mahol 2023-09-26 18:12 ` Nicolas George 2023-09-25 8:24 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Kieran Kunhya 2023-09-26 20:17 ` Rémi Denis-Courmont
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=CAPYw7P7X5NQgWgH7ONxDwdYQK173FR6VFB6242EYTr4P9jQ8vw@mail.gmail.com \ --to=onemda@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