From: Michael 'veremitz' Everitt <gentoo@veremit.xyz>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: Require full $P not just $PN on stable/keyword commit messages
Date: Fri, 1 Nov 2019 20:01:11 +0000 [thread overview]
Message-ID: <89f32b3a-5116-06e0-648c-ee0c610e2d61@veremit.xyz> (raw)
In-Reply-To: <55b42dc1-cbfd-8fa0-8bfd-433e7c92a21f@veremit.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1127 bytes --]
On 01/11/19 19:59, Michael 'veremitz' Everitt wrote:
> Hello,
>
> I've noticed a lot of stabilisation commit messages (and a few keywording
> ones too) simply state the package atom and not the relevant
> release/version. I find this a little meaningless, as unless this is the
> first time the package has ever been either stabilised or keyworded, it is
> reasonable to expect that there is/was some transition point for a package
> from when it first entered the Gentoo Repository.
>
> Therefore, it would be much /more/ useful to have the package-version
> tagged in the commit message, so that you could easily grep logs for when a
> given version of a package was stabilised, and/or keyworded. Granted, this
> is more of-use in a historical context compared to a present (future?!)
> one, but I would argue that it conveys more meaning -with- the version than
> without.
>
> Thoughts from outside peanut gallery?
>
> Michael / veremitz.
>
Also, it's particularly helpful if you have an atom feed of a given
package, to see when versions are stabilised (present and future contexts
covered... ;D)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-11-01 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 19:59 [gentoo-dev] RFC: Require full $P not just $PN on stable/keyword commit messages Michael 'veremitz' Everitt
2019-11-01 20:01 ` Michael 'veremitz' Everitt [this message]
2019-11-01 20:36 ` Matt Turner
2019-11-01 21:11 ` Rich Freeman
2019-11-01 21:34 ` Michael 'veremitz' Everitt
2019-11-01 21:45 ` Mike Gilbert
2019-11-01 21:50 ` Michael 'veremitz' Everitt
2019-11-01 21:47 ` Rich Freeman
2019-11-01 23:08 ` Sergei Trofimovich
2019-11-02 8:54 ` Kent Fredric
2019-11-02 16:25 ` Michael 'veremitz' Everitt
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=89f32b3a-5116-06e0-648c-ee0c610e2d61@veremit.xyz \
--to=gentoo@veremit.xyz \
--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