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

Re: How to keep log history when renaming and changing simultaneously

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 18, 2017, 03:20 UTC
Message-ID
<xmqqr30qflk9.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CA+P7+xpWMdoQj5FxkN=7QKc3UvW77HsTDs5RRZiCg4WVnB4wqA@mail.gmail.com>
Jacob Keller <jacob.keller@gmail.com> writes:
> Unfortunately I don't have a ready link to the message, but there is a
> very good post from early on in Git's development where Linus explains
> why Git does not store rename and copy information in the history.
One of the most important message in the list archive, gmane:217 aka
http://public-inbox.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/
Previous: Jacob Keller
Message 6 of 6 in “How to keep log history when renaming and changing simultaneously”
  1. Urs ThuermannApr 17, 2017
  2. Duy NguyenApr 17, 2017
  3. Igor DjordjevicApr 17, 2017
  4. Urs ThuermannApr 17, 2017
  5. Jacob KellerApr 18, 2017
  6. Junio C HamanoApr 18, 2017

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.