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

Re: Proper tracking of copies in git log and others

From
LKLasse Kärkkäinen <tronic+dfhy@trn.iki.fi>
Date
Jul 14, 2009, 12:19 UTC
Message-ID
<4A5C77E1.7020500@trn.iki.fi>
In-Reply-To
<BLU0-SMTP94B7E43F5EE983A2F9BFA8AE2D0@phx.gbl>
> You could apply that patch and test it out.  Perhaps you could address
> Junio's concern or reignite some interest from the original author.

The patch works fine here and solves my issue. Hopefully it can be made part of the distribution.

Tracking other (intermediate) copies would be a plus but I have absolutely no time to work on git as I am trying to use VCS to reduce my workload, not to increase it :)

Previous: Sean EstabrooksNext: Graeme Geldenhuys
Message 3 of 6 in “Proper tracking of copies in git log and others”
  1. Lasse KärkkäinenJul 4, 2009
  2. Sean EstabrooksJul 4, 2009
  3. Lasse KärkkäinenJul 14, 2009
  4. Graeme GeldenhuysJul 7, 2009
  5. Michael J GruberJul 7, 2009
  6. Avery PennarunJul 7, 2009

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.