git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Stepping through a single file's history

From
PHPete Harlan <pgit@pcharlan.com>
Date
Jan 31, 2010, 08:26 UTC
Message-ID
<4B653E9F.2080109@pcharlan.com>
In-Reply-To
<43d8ce651001281758x79965b5fn8760b69d4fe82a36@mail.gmail.com>
On 01/28/2010 05:58 PM, John Tapsell wrote:
Show 19 quoted lines
> 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

Have you tried "git log -Sfoo filename", which finds commits that changed the number of occurrances of string "foo" in filename? I've found that quite useful in digging up deleted code.

It's not as thorough as grepping "git log -p filename", but in practice I've found it very effective.

--Pete
Previous: John Tapsell
Message 4 of 4 in “Stepping through a single file's history”
  1. Ron GarretJan 29, 2010
  2. John TapsellJan 29, 2010
  3. John TapsellJan 29, 2010
  4. Pete HarlanJan 31, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.