> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > James Almer > Sent: Tuesday, January 21, 2025 3:57 AM > To: ffmpeg-devel@ffmpeg.org > Subject: Re: [FFmpeg-devel] Regarding Git Tooling > > I don't think Forgejo's comment section for commits, bugs and MRs is > good enough for discussion, so i doubt the ML would go anywhere. It > will > just stop being used for patches and reviews as MRs would replace > them.
Is it not like GitHub where you can add review comments directly at the corresponding code lines? One essential ability there is that when multiple iterations of patches are sent, you can still see the review comments of the previous version, so you easily see and verify whether it has been resolved. Also, when a reviewer has marked a file as reviewed and there's an update to the patchset, the "viewed" marker gets cleared only if the file is different from the last time you reviewed it. That's highly useful as reviewers don't need to go through the whole patchset again on each update. If you say the discussion would still happen on the ML, how can this work when the code is elsewhere (not on the ML)? 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-requ...@ffmpeg.org with subject "unsubscribe".
