public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lucio Sauer <watermanpaint@posteo.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Commit tags for resolutions OBSOLETE, PKGREMOVED
Date: Mon, 17 Jun 2024 09:50:29 +0000	[thread overview]
Message-ID: <yc4qtkmntsxuignxwt4y3r2jema2widxbig52ynmmpuaawrnyo@halg6tey35tn> (raw)

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

Hi,

I wrote patches for infra's git hooks[1] and pkgdev[2] that add two new
commit tags to support the automatic closure of bugs with resolutions
other than FIXED.
However, I am not entirely convinced that the meaning of the chosen tags
is self-evident enough for a third party to understand them at a glance.

Feel free to comment on my propsals or suggest alternatives! You'll
hopefully be using them frequently :)

> Orphans: https://bugs.gentoo.org/####

This commit removes the (last remaining) package that has been affected by
this bug. The bug will be closed with resolution PKGREMOVED.
Unknowing users might think that the bug's assignee will be removed
instead.

Sam also suggested "Removed:" and "Last-rited:"[3].
In my opinion, they don't convey that it's the underlying package that
is being remvoed and not the bug itself.

> Antiquates: https://bugs.gentoo.org/####

This commit removes ebuilds and newer versions of the program are no
longer affected or it drops support for the problematic feature. This
bug will be closed with resolution OBSOLETE.
The tag may more commonly be understood as 'makes old-fashioned', which
doesn't really make sense in this context. Pkgdev would only provide the
long option `--antiq`, which would be a bit shorter than `--obsoletes`.

[1]: https://git.sr.ht/~antecrescent/gentoo-githooks/commit/248ba38802abd9e115a2f602a0cd82b32d16c914
[2]: https://github.com/antecrescent/pkgdev/commit/8e1d84971f0f6c3f638381477de9d99f0c1b2ef3
[3]: https://marc.info/?l=gentoo-dev&m=170737555732280&w=2

Best
-- 
Lucio Sauer

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

             reply	other threads:[~2024-06-17  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  9:50 Lucio Sauer [this message]
2024-06-17 11:50 ` [gentoo-dev] Commit tags for resolutions OBSOLETE, PKGREMOVED Michał Górny
2024-06-17 15:11   ` Ulrich Mueller
2024-06-17 20:57     ` Ionen Wolkens
2024-06-18  0:47       ` Lucio Sauer

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=yc4qtkmntsxuignxwt4y3r2jema2widxbig52ynmmpuaawrnyo@halg6tey35tn \
    --to=watermanpaint@posteo.net \
    --cc=gentoo-dev@lists.gentoo.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox