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

Re: git-diff-tree rename detection for single file

From
Junio C Hamano <junkio@cox.net>
Date
Oct 19, 2005, 05:20 UTC
Message-ID
<7virvuhylm.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0510182004100.3369@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> See what I'm saying?
> ...
> The performance impact of pruning the pathnames _before_ diffing them was 
> absolutely staggering. You couldn't reasonably do a "git-whatchanged -p" 

Yes, I understood and agreed to that logic on May 27th. That's why the message you are responding said we could add a new flag, to give the choice to the user to accept full-tree scan.

The "diff-tree --stdin that follows rename history" example might want to have some change in either the core side of diff, or in the rev-list. It may help to have both. I still haven't thought through the issues.

BTW, I really liked your example that piped multiple diff-trees together. That is a neat trick.

Previous: Linus TorvaldsNext: Nicolas Pitre
Message 5 of 6 in “git-diff-tree rename detection for single file”
  1. David HoOct 18, 2005
  2. Junio C HamanoOct 18, 2005
  3. Junio C HamanoOct 19, 2005
  4. Linus TorvaldsOct 19, 2005
  5. Junio C HamanoOct 19, 2005
  6. Nicolas PitreOct 19, 2005

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.