On Tue, Jul 29, 2025 at 11:40 PM Michael Niedermayer <mich...@niedermayer.cc> wrote: > > On Tue, Jul 29, 2025 at 10:04:51PM +0100, Frank Plowman wrote: > > On 28/07/2025 15:20, Michael Niedermayer wrote: > > > Hi > > > > > > regression: issue aaddresses a regression > > > bug: something is not working > > > > > > This is inconsistent > > > Label X cannot sometimes mean "X is removed" and "X is added" > > > > > > bug seems meaning that the PR adds a bug > > > regression seems meaning that the PR removes a regression > > > > > > IMO this should be done consistently > > > a PR can have bugs and it can fix bugs > > > a PR can cause regressions and it can fix regressions > > > > > > thx > > > > > > > Slightly tangential, but labels to say "this fix should be backported to > > release X" would be useful. > > A label thats added by a human > A label that a human must search for > A label that a human must clear after a commit is backported > > is not usefull > > A system that on a single click shows a list of > commit hashes that have not yet been backported > and once a commit is backported it automtaically disappears from > the list, can be usefull.
You can do that by making a MR between the two branches: https://code.ffmpeg.org/kierank/FFmpeg/compare/release/7.1...master Kieran _______________________________________________ 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".