From: Andreas Schwab <schwab@linux-m68k.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: git@vger.kernel.org
Subject: Re: Most recent revision that contains a string
Date: Sun, 21 Aug 2016 10:13:33 +0200 [thread overview]
Message-ID: <m2mvk6iloy.fsf@linux-m68k.org> (raw)
In-Reply-To: <20160821013040.4sfmg2v7rcovxxmb@x> (Josh Triplett's message of "Sat, 20 Aug 2016 18:30:42 -0700")
On Aug 20 2016, Josh Triplett <josh@joshtriplett.org> wrote:
> If you want to find a change that introduces or removes a particular
> string, you could use "git log -S". That doesn't allow regexes,
It does, actually, see --pickaxe-regex.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-08-21 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 21:41 Most recent revision that contains a string Nikolaus Rath
2016-08-21 1:30 ` Josh Triplett
2016-08-21 8:13 ` Andreas Schwab [this message]
2016-08-21 8:48 ` Josh Triplett
2016-08-21 2:46 ` Eric Wong
2016-08-22 18:06 ` Nikolaus Rath
2016-08-23 19:36 ` 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=m2mvk6iloy.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=josh@joshtriplett.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;
as well as URLs for NNTP newsgroup(s).