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

Re: Tracking files across tree reorganizations

From
Junio C Hamano <junkio@cox.net>
Date
Dec 15, 2005, 00:36 UTC
Message-ID
<7vd5jzurfi.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<43A0AE6B.3040309@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> HOWEVER, I maintain that this is unnecessary (and, as Linus has pointed 
> out several time, losing) -- we already detect renames without relying 
> on commit-time metadata.  If it's too expensive to generate the metadata 
> on every merge, it can be cached.
I agree; I was wondering why you brought it up again.
Previous: H. Peter AnvinNext: H. Peter Anvin
Message 8 of 13 in “Tracking files across tree reorganizations”
  1. H. Peter AnvinDec 14, 2005
  2. Petr BaudisDec 14, 2005
  3. H. Peter AnvinDec 14, 2005
  4. Petr BaudisDec 14, 2005
  5. H. Peter AnvinDec 14, 2005
  6. Linus TorvaldsDec 14, 2005
  7. H. Peter AnvinDec 14, 2005
  8. Junio C HamanoDec 15, 2005
  9. H. Peter AnvinDec 15, 2005
  10. Petr BaudisDec 15, 2005
  11. Martin LanghoffDec 15, 2005
  12. Martin LanghoffDec 15, 2005
  13. H. Peter AnvinDec 15, 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.