From: epirat07@gmail.com To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] STF SoWs Date: Thu, 08 Feb 2024 13:42:13 +0100 Message-ID: <9FD31196-6915-4EE8-AF6F-F28C7A568D5F@gmail.com> (raw) In-Reply-To: <ZcTJ+tNHbWUZJQLS@phare.normalesup.org> On 8 Feb 2024, at 13:32, Nicolas George wrote: > Leo Izen (12024-02-07): >> I don't think this is really a fair statement to make. We have lots of >> potential reviewers subscribed to this list but very few people actually >> review code, and those that do review code are expected to provide some sort >> of technical objection or reason why it shouldn't be merged. A random >> subscriber without commit access posting "Nak" on a patch without explaining >> why isn't grounds to block it. > > A random subscriber cannot do that, but if they are thick as thieves > with the people who managed to gain control of the committees, so that Can you maybe stop crying about that things did not went your way on every topic slightly related to FFmpeg „politics“ on this list? This is getting so annoying… The amount of times I had to read your absurd insinuations about there being some „conspiracy“ to take over the project… > they can be sure the tech will side with them and they can threaten you > if you point that their objections are flimsy a little too clearly, then > they can block your patch with a vague “it does not belong in ffmpeg”, > that does require a lot less effort than reviewing. > > Regards, > > -- > 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:[~2024-02-08 12:42 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-06 2:06 Michael Niedermayer 2024-02-06 14:18 ` Ronald S. Bultje 2024-02-06 15:04 ` Vittorio Giovara 2024-02-06 15:14 ` Michael Niedermayer 2024-02-06 15:21 ` Ronald S. Bultje 2024-02-06 15:26 ` Michael Niedermayer 2024-02-06 15:41 ` Michael Niedermayer 2024-02-06 16:04 ` Niklas Haas 2024-02-06 17:02 ` Ronald S. Bultje 2024-02-06 18:17 ` Michael Niedermayer 2024-02-06 18:48 ` Paul B Mahol 2024-02-07 12:16 ` Nicolas George 2024-02-07 13:11 ` Rémi Denis-Courmont 2024-02-06 20:53 ` Ronald S. Bultje 2024-02-06 21:23 ` Michael Niedermayer 2024-02-06 21:39 ` Ronald S. Bultje 2024-02-06 23:04 ` Michael Niedermayer 2024-02-07 1:38 ` Ronald S. Bultje 2024-02-07 12:58 ` Michael Niedermayer 2024-02-07 13:08 ` Ronald S. Bultje 2024-02-07 14:44 ` Michael Niedermayer 2024-02-07 17:31 ` Ronald S. Bultje 2024-02-08 4:08 ` Michael Niedermayer 2024-02-07 19:01 ` Leo Izen 2024-02-07 19:53 ` Michael Niedermayer 2024-02-08 12:32 ` Nicolas George 2024-02-08 12:42 ` epirat07 [this message] [not found] ` <1C84A3B8-51FD-4E46-8A61-B0A047606152@cosmin.at> 2024-02-07 2:28 ` Cosmin Stejerean via ffmpeg-devel 2024-02-06 18:48 ` Niklas Haas 2024-02-06 15:59 ` Niklas Haas 2024-02-06 14:57 ` Vittorio Giovara 2024-02-06 15:25 ` Michael Niedermayer
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=9FD31196-6915-4EE8-AF6F-F28C7A568D5F@gmail.com \ --to=epirat07@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