From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] The "bad" Patch Date: Sat, 31 May 2025 16:59:00 +0000 Message-ID: <DM8P223MB0365988D63FA7DF0CCF58AAEBA60A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <DM8P223MB036575864A9E6924CCC1A2B5BA60A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (this is the 2nd last message) Final Chapter ============= Some people here don't like me - that's okay. I'm honest, direct, I say what I'm thinking, often not very diplomatic, and I know which results it causes sometimes. But that a few people kind-of tried campaigning against me - even neglecting facts against better knowledge - that came to me as a surprise, given that I'm not attacking anybody personally (except Nicolas, who's begging for it). I don't know what I've done which might have pulled a trigger for some, so I can't comment. Let's get to the cast of the final chapter: - Lynne - Nicolas George - Kieran Kunyar They were acting as some kind of boosters, blowing up and spreading things, including false facts or distorted views of the situation. Lynne ===== I had sensed a hostile attitude for some time which became eventually visible here, one week before patchset was pushed: Quotes: IRC, 2025-05-08 11:20 <Lynne> I think it was too early to give softworkz push access What's remarkable is that I haven't pushed anything between 2025-05-03 and 2025-05-15. I had just sent patches to the ML that day.. - so, this statement cannot have been about a pushed commit. I might be mistaken, but it very much looked to me like she had just been waiting until I'd make some (seeming) mistake. After I had pushed the patchset: IRC, 2025-05-16 11:25 <Lynne> softworkz: you've been refusing to use proper submission procedures, tried to introduce your own, you've pushed bad patches and did not even consider that calling external programs from a binary directly was inherently bad. 11:26 <Lynne> I don't think you deserve your push privileges 11:27 <Lynne> softworkz: last month you even had to publicly ask on the mailing list about a policy which pretty much everyone understood A full load thrown at me, all points having turned out to be pointless, also accusing me for asking a question on the mailing list - like a kind of failed attempt for finding once another bad thing I would have done. Ref "bad patch": this conversation Ref "proper submission procedures": https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343806.html Ref "Question on the Mailing List": https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343107.html When I'd be asked what a bad patch is - then I'd say that a patch that is pushed, which breaks FATE is definitely a "bad patch". As we know now that my patch 15/15 was NOT bad and I've never pushed a commit that breaks FATE, this means that _my_ "bad-patch-count" is zero. While not everybody has a count of zero, I'm not going to make a big thing out of it. Nicolas George ============== He appears to be desperately looking for a slave developer who is looking up to him and follows his instructions. Why he doesn't realize that I'm the least suitable person on the planet for this figment, is a mystery to me. I'm still surprised that he made it into this cast. Normally, he is running his own show without jumping on others' trains. Seems he couldn't resist to this opportunity. I'm pretty sure he had looked at the patchset. He followed the development and revisions more than anybody else and made a lot of comments, to several commits and was involved in the discussions about the AVTextFormat API. Quotes: 2025-05-22 I think giving softworkz the authority to decide if his own patches are ready for inclusion was premature. 2025-05-16 [to Michael] In particular I think you granted Git access too soon. A track record of multiple non-trivial patches and useful reviews should have been necessary. => He knows my subtitle filtering patchset and he has seen many reviews I did in earlier years. => So, this is just feigned ignorance, disguised under the guise of reason. Kieran Kunhya ============= I don't know much about him, other than sometimes making aggressive posts. He came right out of nowhere and started campaigning against me and the whole patchset. Obviously, he had never looked at it before. Quotes: 2025-05-22 I really wonder how you can't be embarrassed sending what imo is the worst patchset in the history of the project. 2025-05-22 A patchset so bad, people who quit the project like Derek came back to clean up your mess. Almost hilarious, if it wouldn't be a serious matter with a clear intention to defame me. (next message will be the final) Best regards, sw _______________________________________________ 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:[~2025-05-31 16:59 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-28 15:24 softworkz . 2025-05-28 17:34 ` Rémi Denis-Courmont 2025-05-28 18:01 ` softworkz . 2025-05-28 18:09 ` softworkz . 2025-05-28 18:27 ` Marton Balint 2025-05-28 18:46 ` softworkz . 2025-05-29 2:59 ` softworkz . 2025-05-29 9:55 ` Nicolas George 2025-05-31 11:44 ` softworkz . 2025-05-31 16:21 ` Mark Thompson 2025-05-31 18:28 ` softworkz . 2025-05-31 20:26 ` Mark Thompson 2025-06-02 6:09 ` softworkz . 2025-06-02 7:31 ` softworkz . 2025-05-31 16:59 ` softworkz . [this message] 2025-05-31 17:34 ` softworkz . 2025-06-01 23:21 ` Michael Niedermayer 2025-06-01 23:51 ` softworkz . 2025-06-02 7:57 ` Nicolas George 2025-06-02 9:31 ` softworkz . 2025-06-02 10:18 ` softworkz . 2025-06-02 10:49 ` Nicolas George 2025-06-02 19:30 ` softworkz . 2025-06-02 21:26 ` softworkz . 2025-06-02 19:34 ` Michael Niedermayer 2025-06-02 21:22 ` softworkz . 2025-06-03 1:06 ` Michael Niedermayer 2025-06-01 23:56 ` softworkz . 2025-05-31 18:38 ` Kieran Kunhya via ffmpeg-devel 2025-05-29 14:43 ` Nicolas George 2025-05-30 3:42 ` softworkz . 2025-05-31 19:31 ` Leo Izen 2025-05-31 19:34 ` Marvin Scholz 2025-05-31 20:08 ` softworkz . 2025-05-31 20:13 ` softworkz .
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=DM8P223MB0365988D63FA7DF0CCF58AAEBA60A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.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