On Thu, 18 Sep 2025 01:52:31 -0700 Jacob Lifshay via ffmpeg-devel <[email protected]> wrote: > On Thu, Sep 18, 2025 at 12:03 AM Nicolas George via ffmpeg-devel > <[email protected]> wrote: > > > > Timo Rothenpieler via ffmpeg-devel (HE12025-09-18): > > > The problem is they can be very frequent. And not only force pushes. > > > So the current implementation is a compromise between visibility and > > > spam-level. > > > > They are not more frequent than v2, v3, etc., used to be, and therefore > > below acceptable spam threshold. > > I don't know about you, but whenever I'm developing code, I sometimes > push new changes multiple times in a day and then only ask for more > review after I'm done developing whatever thing I'm working on, maybe > after several days -- pushing code is way more often than I might send > out patch sets via mail since that tends to directly imply I want the > latest code to be reviewed now and I think it's ready, rather than > just git pushing so the code is on the server in case I want to access > it from a different computer or just see if CI passes or something.
We could send a copy to the ML whenever the PR author requests a review (via the web interface). Normally, in a scenario like the above, I would first make any changes until I'm happy and then (re-)request a review. > > Jacob > _______________________________________________ > ffmpeg-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
