From: Eric Raible <raible@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: RFH - git-log variant that _does_ search through diffs
Date: Tue, 30 Jun 2009 11:05:08 -0700 [thread overview]
Message-ID: <279b37b20906301105tf92f471g6146a083ba2e2882@mail.gmail.com> (raw)
In-Reply-To: <20090630040337.GA23741@sigio.peff.net>
On Mon, Jun 29, 2009 at 9:03 PM, Jeff King<peff@peff.net> wrote:
> You can at least combine rev-list and diff into one command, and grep
> like this (for 'foo'):
>
> git log -z -p | perl -0ne 'print if /^[-+].*foo/m' | tr '\0' '\n'
>
> -Peff
Thank you, that will do very nicely as a starting point.
What I _really_ want is the subset of all commits containing foo
who's oneline commit message doesn't match a given regexp.
So I'm used something like this to extract the commits of interest:
git log -z -p | perl -0ne 'print if /^[-+].*foo/m' | tr '\0' '\n' |
grep "^commit [0-9a-f]" | awk '{print $2}' |
xargs -n1 git log --pretty=oneline -1 |
grep -v dont_want
In this specific case of wanting to ignore particular commits a loop
over git-rev-list might yield a better solution. But the 'git-log | perl | tr'
snippet is a nice idiom for day-to-day use.
next prev parent reply other threads:[~2009-06-30 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 0:08 RFH - git-log variant that _does_ search through diffs Eric Raible
2009-06-30 4:03 ` Jeff King
2009-06-30 8:09 ` Junio C Hamano
2009-06-30 18:06 ` Eric Raible
2009-06-30 18:05 ` Eric Raible [this message]
2009-06-30 19:31 ` Jeff King
2009-06-30 21:22 ` Eric Raible
2009-06-30 21:34 ` Eric Raible
2009-07-01 7:02 ` Jeff King
2009-07-01 7:26 ` [PATCH 1/2] log-tree: fix confusing comment Jeff King
2009-07-01 7:26 ` [RFC/PATCH 2/2] fix missing NUL termination with pretty=tformat Jeff King
2009-07-01 8:27 ` Junio C Hamano
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=279b37b20906301105tf92f471g6146a083ba2e2882@mail.gmail.com \
--to=raible@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).