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

Re: [PATCH 2/2] Teach name-rev to identify revisions containing a certain blob

From
Junio C Hamano <junkio@cox.net>
Date
Feb 18, 2007, 08:48 UTC
Message-ID
<7vejonj1h3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<7vmz3bj248.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 8 quoted lines
> [Footnote]
>
> *1* To find a revision that had a particular object at a known
> path, you should be able to do:
>
> 	git rev-list <starting refs> |
>       git diff-tree --stdin --raw -r -Z |
> 	grep -z that-object-name
Sheesh, please add "-- <path>" after "-Z".
>
> but an earlier commit abd4e222 needs to be further enhanced to
> add -Z option that means "output fields are not NUL terminated,
> output records are", which did not happen.
Previous: Junio C HamanoNext: Johannes Schindelin
Message 8 of 9 in “Teach name-rev to identify revisions containing a certain blob”
  1. 2/2 Teach name-rev to identify revisions containing a certain blobJohannes Schindelin, Feb 17, 2007
  2. Junio C HamanoFeb 17, 2007
  3. Johannes SchindelinFeb 17, 2007
  4. Johannes SchindelinFeb 18, 2007
  5. Junio C HamanoFeb 17, 2007
  6. Johannes SchindelinFeb 17, 2007
  7. Junio C HamanoFeb 18, 2007
  8. Junio C HamanoFeb 18, 2007
  9. Johannes SchindelinFeb 18, 2007

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.