From: Kacper Michajlow <kasper93@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] rebase bugs? Date: Sat, 9 Aug 2025 16:00:32 +0200 Message-ID: <CABPLASRRH6k86Y_E4s6fyQBBfcqCXb42VcqWfyj-kKq83Wo8AQ@mail.gmail.com> (raw) In-Reply-To: <20250809121451.GR29660@pb2> On Sat, 9 Aug 2025 at 14:15, Michael Niedermayer <michael@niedermayer.cc> wrote: > > Hi > > On Sat, Aug 09, 2025 at 07:02:29AM +0200, Kacper Michajlow wrote: > [...] > > > ... in a > > corporate environment, things like that would never happen ... > > yeah, never ever seen a bug in software in a corporate environment No need to be sarcastic about it. And no need to splice my response to fit your response. I said > things like that would never happen in more mature software It’s a numbers game. Even you noticed that it didn’t take long to find a bug in Forgejo. We merged <100 PR, many outside of the UI, and already found a rebase bug in a trivial 2 commit PR. That doesn't give me confidence in the integrity of the ffmpeg repository if such issues occur. Additionally there is a completely not working commit signing. Code forges work as long as you can trust them to do the right thing. Otherwise, I’d rather do things manually. - Kacper _______________________________________________ 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-08-09 14:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-08-08 23:09 Michael Niedermayer 2025-08-08 23:18 ` James Almer 2025-08-08 23:28 ` Michael Niedermayer 2025-08-09 5:02 ` Kacper Michajlow 2025-08-09 12:14 ` Michael Niedermayer 2025-08-09 14:00 ` Kacper Michajlow [this message] 2025-08-09 14:18 ` Michael Niedermayer 2025-08-09 12:18 ` 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=CABPLASRRH6k86Y_E4s6fyQBBfcqCXb42VcqWfyj-kKq83Wo8AQ@mail.gmail.com \ --to=kasper93@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