Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] forgejo labels
Date: Wed, 30 Jul 2025 00:40:35 +0200
Message-ID: <20250729224035.GN29660@pb2> (raw)
In-Reply-To: <acd5261c-2ab6-4655-9be7-a9ee073ec2cf@frankplowman.com>


[-- Attachment #1.1: Type: text/plain, Size: 1298 bytes --]

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.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2025-07-29 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 14:20 Michael Niedermayer
2025-07-28 14:40 ` Diederick C. Niehorster
2025-07-28 16:15   ` Timo Rothenpieler
2025-07-28 17:24     ` Michael Niedermayer
2025-07-28 17:37       ` Timo Rothenpieler
2025-07-30  5:37         ` Lynne
2025-07-29 21:04 ` Frank Plowman
2025-07-29 22:40   ` Michael Niedermayer [this message]
2025-07-29 23:18     ` Kieran Kunhya via ffmpeg-devel

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=20250729224035.GN29660@pb2 \
    --to=michael@niedermayer.cc \
    --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