From: Nicolas George <george@nsup.org> 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 22:46:25 +0100 Message-ID: <ZUlescW++Hs7OT8D@phare.normalesup.org> (raw) In-Reply-To: <CABLWnS-OTa+mDjiHvup6C8cbzU9YTaT-NmyrL1s8WuhzcoC2Lw@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --] Vittorio Giovara (12023-11-06): > Nice try but pointing out your logical fallacies is not being rude, but > rather is just showing you how easily your message can be misinterpreted, You have done nothing of the sort. You have just misrepresented my words, showing that you decided to barge into a conversation without knowing its details. > And yes, asking for time when you yourself do not provide a > timeline is equivalent to vetoing a patch (indefinitely too, since you > yourself say you "will review this issue when [you] have the time", which > could very well be never). And now you are accusing me of outright dishonesty. Better and better. > I feel like, once again, we've exhausted this topic You have exhausted because you barged in without knowing the first thing about it. > Please justify your objections to the proposed solution, I have already done so, but again you neglected to read it: if there is a bug, it is in the framework code. -- Nicolas George [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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 21:46 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 [this message] 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=ZUlescW++Hs7OT8D@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