From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/buffersrc: switch to activate Date: Mon, 6 Nov 2023 15:45:15 -0500 Message-ID: <CABLWnS-zboTO7pq0x1sHe3E+bHg6Dok_FsD_E12MR3QVq424WA@mail.gmail.com> (raw) In-Reply-To: <ZUlMbKQoj7JFezRP@phare.normalesup.org> On Mon, Nov 6, 2023 at 3:28 PM Nicolas George <george@nsup.org> wrote: > Vittorio Giovara (12023-11-06): > > You gave no indication you were willing to, and I thought he gave you > time > > Bullshit. Please do not intervene in a thread when you do not know what > is going on at all. Paul has been repeatedly rude and threatened to push > before review, yet it is towards me you address your criticism. > Please as a non-native English speaker to another non-native English speaker, you may miss that this comes off extremely aggressive and offensive especially in text form. And this is a public mailing list, everybody is allowed to intervene in every thread -- if you don't like it, take your discussion offline. There is no need for some language or behavior, while I can understand being mad at Paul, the community, or the world, please make a minimum of effort to keep communication polite, and efficient, as stated multiple times. Belligerence will take you nowhere. > > on the other thread for a related bug and you used it for mind games. > > Anyway, usually code trumps words, so the course I'd suggest is agreeing > on > > a feasible time window, and if you can get a better patch out, then > submit > > it, otherwise Paul's can go in. > > No. I will review this issue when I have the time and Paul will wait. > This is how it works. Invalid patches do not go in just because the > maintainer is busy or sick. > That is not how it works, you cannot indefinitely veto a patch just because you think it is invalid. Your concerns in the first email were addressed in Paul's reply. In the other thread, 3 people verified the presence of the bug while you insisted it wasn't there, while also confirming the patch is valid. If you can provide further counterpoints to Paul's explanation, please share them instead of silence, if you have anything substantial (code wise) to add please do so, otherwise let the patch in. This bickering on the list cannot continue. -- Vittorio _______________________________________________ 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-11-06 20:45 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-04 19:07 Paul B Mahol 2023-11-04 19:06 ` Nicolas George 2023-11-04 20:05 ` Paul B Mahol 2023-11-06 18:54 ` Paul B Mahol 2023-11-06 18:50 ` Nicolas George 2023-11-06 19:59 ` Vittorio Giovara 2023-11-06 20:07 ` Nicolas George 2023-11-06 20:21 ` Vittorio Giovara 2023-11-06 20:28 ` Nicolas George 2023-11-06 20:45 ` Vittorio Giovara [this message] 2023-11-06 20:50 ` Nicolas George 2023-11-06 21:22 ` Vittorio Giovara 2023-11-06 21:46 ` Nicolas George 2023-11-06 22:26 ` Vittorio Giovara 2023-11-06 22:48 ` Nicolas George 2023-11-06 23:03 ` Vittorio Giovara 2023-11-06 23:05 ` Nicolas George 2023-11-06 23:20 ` Vittorio Giovara 2023-11-07 7:44 ` Nicolas George 2023-11-07 9:20 ` Vittorio Giovara 2023-11-07 9:35 ` Nicolas George 2023-11-07 20:05 ` Paul B Mahol 2023-11-07 21:50 ` Nicolas George 2023-11-07 22:40 ` Sean McGovern 2023-11-07 22:50 ` Nicolas George 2023-11-08 13:53 ` Nicolas George 2023-11-08 18:28 ` Paul B Mahol 2023-11-08 18:22 ` Nicolas George 2023-11-11 18:03 ` Paul B Mahol 2023-11-11 18:27 ` Nicolas George 2023-11-11 18:38 ` Vittorio Giovara 2023-11-11 18:42 ` Nicolas George 2023-11-11 18:55 ` Vittorio Giovara 2023-11-11 19:03 ` Nicolas George 2023-11-11 19:31 ` Vittorio Giovara 2023-11-12 10:02 ` Nicolas George 2023-11-12 16:36 ` Michael Niedermayer 2023-11-12 20:19 ` Paul B Mahol 2023-11-13 16:59 ` Michael Niedermayer 2023-11-13 17:45 ` Sean McGovern 2023-11-13 18:42 ` Zhao Zhili 2023-11-13 19:03 ` Paul B Mahol 2023-11-13 21:32 ` Nicolas George 2023-11-13 23:59 ` Paul B Mahol 2023-11-12 1:46 ` Paul B Mahol 2023-11-12 10:00 ` 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=CABLWnS-zboTO7pq0x1sHe3E+bHg6Dok_FsD_E12MR3QVq424WA@mail.gmail.com \ --to=vittorio.giovara@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