From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/buffersrc: switch to activate Date: Mon, 13 Nov 2023 20:03:02 +0100 Message-ID: <CAPYw7P4p8BjS88HzTuW_4H0SZfU2htojQo+cyy1n=bPtspf8uQ@mail.gmail.com> (raw) In-Reply-To: <20231113165942.GJ3543730@pb2> On Mon, Nov 13, 2023 at 6:00 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > On Sun, Nov 12, 2023 at 09:19:57PM +0100, Paul B Mahol wrote: > > On Sun, Nov 12, 2023 at 5:37 PM Michael Niedermayer < > michael@niedermayer.cc> > > wrote: > > > > > On Sun, Nov 12, 2023 at 11:02:49AM +0100, Nicolas George wrote: > > > > Vittorio Giovara (12023-11-11): > > > > > Nice victimization, but "i'm behaving poorly because the other > person > > > is a > > > > > meanie" is a childish argument > > > > > > > > Mock all your want, the fact that you attacked me even though I was > just > > > > replying and not even told Paul to stop his childish games proves you > > > > are biassed beyond all credibility. > > > > > > > > > I am genuinely concerned for whatever reason is pushing you to use > > > such an > > > > > alienating and toxic language, yes. > > > > > > > > Yeah, right. You mocking somebody's mental health was way more > > > > inappropriate than anything that I or Paul ever wrote. > > > > > > Vittorio, Nicolas, Paul. > > > > > > guys i love you all but can you rest this thread until we have a new > > > community committee ? > > > > > > thanks! > > > > > > PS: if there are technical questions and you want, there is a technical > > > committe that could look at it. > > > (At least IMHO the TC is fully functional, thats just my personal > oppinion > > > iam not speaking for the TC here) > > > > > > > > > You are blocking my patch. > > You should be ashamed. > > dear patch iam ashamed but iam not actually blocking you. > Maybe you can forgive me if i provide this short ode to you > > Oh, Paul's Patch, you sly little thing, > A fix for libavfilter, oh joy it brings. > In the world of code, where bugs do dwell, > You swoop in gracefully, breaking their spell. > > With your lines of logic, so neat and clean, > You dance through the bugs like a code routine. > Oh, Paul's Patch, you're a hero in disguise, > Saving us from errors, what a pleasant surprise! > > You sneak into the code, like a ninja in the night, > Fixing issues left and right, oh what a sight. > Libavfilter trembles, but not in fear, > For with Paul's Patch, victory is near. > > Oh, patch so fine, with your bug-crushing might, > You turn errors into pixels of pure delight. > Paul's Patch, the troubleshooter supreme, > In the open source world, you reign supreme. > > Programmers cheer, and users applaud, > For with Paul's Patch, we're never flawed. > So here's to you, oh mighty fixer-upper, > In the kingdom of code, you're the top-drawer. > > To Paul's Patch, a toast we raise, > In the realm of software, you set ablaze. > For every bug quivered, and every glitch shivered, > Thanks to Paul's Patch, we code delivered! > If this is ChatGPT, I'm even more sad. > > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Many things microsoft did are stupid, but not doing something just because > microsoft did it is even more stupid. If everything ms did were stupid they > would be bankrupt already. > _______________________________________________ > 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-11-13 18:55 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 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 [this message] 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='CAPYw7P4p8BjS88HzTuW_4H0SZfU2htojQo+cyy1n=bPtspf8uQ@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