From: John Tapsell <johnflux@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: Stepping through a single file's history
Date: Fri, 29 Jan 2010 01:58:56 +0000 [thread overview]
Message-ID: <43d8ce651001281758x79965b5fn8760b69d4fe82a36@mail.gmail.com> (raw)
In-Reply-To: <5699F80A-4B27-4BAB-BEE8-5C48938A970B@flownet.com>
2010/1/29 Ron Garret <ron@flownet.com>:
> Hello,
>
> Is there an easy way to step through the history of a single file? To be more specific:
...
> (The use case here is remembering that back in the day there was some useful code in this file that I want to retrieve, but not remembering exactly when it was deleted. So I want to step back through this file's history and do diffs against HEAD.)
How about simply doing:
git log -p filename
and then you can search by pressing "/" and then typing whatever you remember.
John
next prev parent reply other threads:[~2010-01-29 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 1:28 Stepping through a single file's history Ron Garret
2010-01-29 1:58 ` John Tapsell [this message]
2010-01-29 3:47 ` John Tapsell
2010-01-31 8:26 ` Pete Harlan
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=43d8ce651001281758x79965b5fn8760b69d4fe82a36@mail.gmail.com \
--to=johnflux@gmail.com \
--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.
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).