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

Re: git-log --full-history renamed-file

From
Junio C Hamano <junkio@cox.net>
Date
Mar 10, 2007, 02:14 UTC
Message-ID
<7v6499zvyl.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<est24q$p4n$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> writes:
Show 5 quoted lines
> By the way, while it is fairly easy to follow one file, it is hard
> to follow directory or glob... and there is a trouble that one file
> might come from two files (as concatenation for example; but I don't
> think git can detect it with default values of rename detection
> heuristics).

That's why Linus's proof-of-concept is based on the git-blame engine.

Previous: Jakub NarebskiNext: Linus Torvalds
Message 5 of 8 in “git-log --full-history renamed-file”
  1. Jim MeyeringMar 9, 2007
  2. Linus TorvaldsMar 9, 2007
  3. Junio C HamanoMar 10, 2007
  4. Jakub NarebskiMar 10, 2007
  5. Junio C HamanoMar 10, 2007
  6. Linus TorvaldsMar 10, 2007
  7. Andy ParkinsMar 10, 2007
  8. Junio C HamanoMar 10, 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.