From: Frank Plowman <post@frankplowman.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] forgejo labels
Date: Tue, 29 Jul 2025 22:04:51 +0100
Message-ID: <acd5261c-2ab6-4655-9be7-a9ee073ec2cf@frankplowman.com> (raw)
In-Reply-To: <20250728142057.GZ29660@pb2>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 623 bytes --]
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.
--
Frank
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1091 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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".
next prev parent reply other threads:[~2025-07-29 21:05 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 [this message]
2025-07-29 22:40 ` Michael Niedermayer
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=acd5261c-2ab6-4655-9be7-a9ee073ec2cf@frankplowman.com \
--to=post@frankplowman.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