From: Rich Freeman <rich0@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:47:51 -0400 [thread overview]
Message-ID: <CAGfcS_mFr40=7U+zF7xym3JUO11r_Q2jPK-wK8COrZgwH2fk9Q@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:
>
> > git log --format=oneline glibc-2.29-r2.ebuild | grep stable
> >
> How well does git handle that when the ebuild is deleted from the tree?
>
git log --format=oneline -- glibc-2.29-r4.ebuild
23d1c015230d9ff44bcdd7b72e00ca3533815fa4 sys-libs/glibc: drop old
f3872a506edc7da0d987bcf0a90d4709945328a7 sys-libs/glibc: restore strip
quirk for 'libpthread.so.0'
650d70eb5d91265329e2f730bc1aed0fa5863db6 sys-libs/glibc: disable
stripping for cross-glibc
e14229b10b513a164f8379ff14cc8c644c071f27 sys-libs/glibc: drop
prepallstrip, bug #587296
fb2fe75af62ad29a44aeba1b8e9e41ce5acb3992 sys-libs/glibc: Add 2.29
revision with compile-locales support
I was too lazy to find something that had stable keywords, but I'm
sure substituting the appropriate filename and grepping would work
fine. The trick is to put the "--" in the command line.
However, you could hardly be blamed for hitting your head against the
wall trying to figure out how to do this. I had to google it as I've
run into this myself. As many have said git is an amazing data model
with a terrible UI.
--
Rich
next prev parent reply other threads:[~2019-11-01 21:48 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
2019-11-01 21:50 ` Michael 'veremitz' Everitt
2019-11-01 21:47 ` Rich Freeman [this message]
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='CAGfcS_mFr40=7U+zF7xym3JUO11r_Q2jPK-wK8COrZgwH2fk9Q@mail.gmail.com' \
--to=rich0@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