From: Nikolaus Rath <Nikolaus@rath.org>
To: Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org
Subject: Re: Most recent revision that contains a string
Date: Mon, 22 Aug 2016 11:06:07 -0700 [thread overview]
Message-ID: <871t1ghe5s.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <20160821024647.GA19536@starla> (Eric Wong's message of "Sun, 21 Aug 2016 02:46:47 +0000")
On Aug 21 2016, Eric Wong <e@80x24.org> wrote:
> Nikolaus Rath <Nikolaus@rath.org> wrote:
>> What's the easiest way to find the most recent revision (of any file in
>> the repository, including those that have been deleted in the current
>> HEAD) that contains a given string?
>
> I normally do something like:
>
> git log -r --raw -p -SSTRING
> git log -r --raw -p -GREGEXP
>
> You can also add --diff-filter=D to filter only on deletes.
Great, thanks!
> Btw, please don't set these headers on kernel.org lists:
>
> Mail-Copies-To: never
> Mail-Followup-To: git@vger.kernel.org
>
> Like any mail server, vger fails from time-to-time and
> reply-to-all prevents it from being a single point of failure.
Huh? If the list-server fails only I will receive the message so it's
still lost for everyone else. But I am more than happy to take this
little risk if it saves me from the nuisance of getting duplicate
responses.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-08-22 18:06 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
2016-08-21 8:48 ` Josh Triplett
2016-08-21 2:46 ` Eric Wong
2016-08-22 18:06 ` Nikolaus Rath [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871t1ghe5s.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=e@80x24.org \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).