From: Mike Gilbert <floppym@gentoo.org>
To: gentoo@veremit.xyz
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] RFC: Require full $P not just $PN on stable/keyword commit messages
Date: Fri, 1 Nov 2019 17:45:10 -0400 [thread overview]
Message-ID: <CAJ0EP40LZmKHnFqDJVzQCt0a4ywc0VmXTAntRi8oO957dTyhfw@mail.gmail.com> (raw)
In-Reply-To: <4ccd5427-2918-344f-4dba-276fd7cbe433@veremit.xyz>
On Fri, Nov 1, 2019 at 5:34 PM Michael 'veremitz' Everitt
<gentoo@veremit.xyz> wrote:
>
> On 01/11/19 21:11, Rich Freeman wrote:
> > On Fri, Nov 1, 2019 at 4:36 PM Matt Turner <mattst88@gentoo.org> wrote:
> >> On Fri, Nov 1, 2019 at 12:59 PM Michael 'veremitz' Everitt
> >> <gentoo@veremit.xyz> wrote:
> >>>
> >>> 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.
> > git log --format=oneline glibc-2.29-r2.ebuild | grep stable
> > 9c04d06d06d51d9c76b3fe5ceb573213769f45ae sys-libs/glibc-2.29-r2: sparc
> > stable, bug 685818
> > b61ab167e82261ed2078c068ba0c2fc3a7b58aa3 sys-libs/glibc: stable
> > 2.29-r2 for hppa, bug #685818
> > fad52f75c759ca326ce0f8c37e227827f01cd2f1 sys-libs/glibc: m68k stable
> > wrt bug #685818
> > 0fe91535a7ba382f10084def5482e61359f201cb sys-libs/glibc: sh stable wrt
> > bug #685818
> > 7b7ec9a6b3355d6111e1a449ca13e24cb6ef0295 sys-libs/glibc: s390 stable
> > wrt bug #685818
> > bcddad6780ead2b44528a4aa1d51107b4a225524 sys-libs/glibc-2.29-r2: alpha stable
> > 2ca6a4b9d647f567d2300e7b90829993d7575b41 sys-libs/glibc: ia64 stable
> > wrt bug #685818
> > e56c3c1f1c0a256c228a59be94869751d7fd31d7 sys-libs/glibc: ppc64 stable
> > wrt bug #685818
> > 52355459ec00b9ca9921bd5f788bad9b95346910 sys-libs/glibc: ppc stable
> > wrt bug #685818
> > 745b07e84b5035576737d3e1a719121d02e53feb sys-libs/glibc: arm stable
> > wrt bug #685818
> > 332fc91e3e72a6dd1b183ce4a19d08b45daa8e00 sys-libs/glibc: x86 stable
> > (bug #685818)
> > 9e06c1242e104b66a532e7d5d919c1b3b1f8343d sys-libs/glibc: arm64 stable
> > (bug #685818)
> > b3ad265998a04a40820d078d25c06b7cb51173ef sys-libs/glibc: amd64 stable
> > wrt bug #685818
> >
> > Seems to work fine for me.
> >
> >
> How well does git handle that when the ebuild is deleted from the tree?
It handles it just fine, though you need to add "--" to disambiguate
it from a ref. For example:
git log --format=oneline --grep=stable -- foo-123.ebuild
next prev parent reply other threads:[~2019-11-01 21:45 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 ` [gentoo-dev] " Michael 'veremitz' Everitt
2019-11-01 20:36 ` [gentoo-dev] " Matt Turner
2019-11-01 21:11 ` Rich Freeman
2019-11-01 21:34 ` Michael 'veremitz' Everitt
2019-11-01 21:45 ` Mike Gilbert [this message]
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=CAJ0EP40LZmKHnFqDJVzQCt0a4ywc0VmXTAntRi8oO957dTyhfw@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo@veremit.xyz \
/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