Gentoo Archives: gentoo-dev

From: Michael 'veremitz' Everitt <gentoo@×××××××.xyz>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: RFC: Require full $P not just $PN on stable/keyword commit messages
Date: Fri, 01 Nov 2019 20:01:25
Message-Id: 89f32b3a-5116-06e0-648c-ee0c610e2d61@veremit.xyz
In Reply to: [gentoo-dev] RFC: Require full $P not just $PN on stable/keyword commit messages by Michael 'veremitz' Everitt
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)

Attachments

File name MIME type
signature.asc application/pgp-signature