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

Re: Git: new feature suggestion

From
Joao Pinto <joao.pinto@synopsys.com>
Date
Jan 19, 2017, 17:55 UTC
Message-ID
<d43abe2b-cd6a-9b08-272f-9dddbb8eccea@synopsys.com>
In-Reply-To
<20170119093313.ea57832dfd1bc7e0b0f1e630@domain007.com>
Hi,
Às 6:33 AM de 1/19/2017, Konstantin Khomoutov escreveu:
Show 36 quoted lines
> On Wed, 18 Jan 2017 10:40:52 +0000
> Joao Pinto <Joao.Pinto@synopsys.com> wrote:
> 
> [...]
>> I have seen a lot of Linux developers avoid this re-organization
>> operations because they would lose the renamed file history, because
>> a new log is created for the new file, even if it is a renamed
>> version of itself. I am sending you this e-mail to suggest the
>> creation of a new feature in Git: when renamed, a file or folder
>> should inherit his parent’s log and a “rename: …” would be
>> automatically created or have some kind of pointer to its “old” form
>> to make history analysis easier.
> 
> Git does not record renames because of its stance that what matters is
> code _of the whole project_ as opposed to its location in a particular
> file.
> 
> Hence with regard to renames Git "works backwards" by detecting them
> dynamically while traversing the history (such as with `git log`
> etc).  This detection uses certain heuristics which can be controlled
> with knobs pointed to by Stefan Beller.
> 
> Still, I welcome you to read the sort-of "reference" post by Linus
> Torvalds [1] in which he explains the reasoning behind this approach
> implemented in Git.  IMO, understanding the reasoning behind the idea
> is much better than just mechanically learning how to use it.
> 
> The whole thread (esp. Torvalds' replies) is worth reading, but that
> particular mail summarizes the whole thing very well.
> 
> (The reference link to it used to be [2], but Gmane is not fully
> recovered to be able to display it.)
> 
> 1. https://urldefense.proofpoint.com/v2/url?u=http-3A__public-2Dinbox.org_git_Pine.LNX.4.58.0504150753440.7211-40ppc970.osdl.org_&d=DwIDaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=s2fO0hii0OGNOv9qQy_HRXy-xAJUD1NNoEcc3io_kx0&m=X0bQCOGTuZF-uq6smPwJDw4Q47qHgjWaewgTHCbhMnM&s=97U97toe9A6XOAJxbhxvWeYpzl-wPw9QvlhQfAEUTdI&e= 
> 2. https://urldefense.proofpoint.com/v2/url?u=http-3A__thread.gmane.org_gmane.comp.version-2Dcontrol.git_27_focus-3D217&d=DwIDaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=s2fO0hii0OGNOv9qQy_HRXy-xAJUD1NNoEcc3io_kx0&m=X0bQCOGTuZF-uq6smPwJDw4Q47qHgjWaewgTHCbhMnM&s=agYFOBCbLeaKAB6frWWzcwHkZyrMZLW4ExgDxzQyVlI&e= 
> 
Thank you very much for the info!
Joao
Previous: Junio C HamanoNext: Linus Torvalds
Message 6 of 15 in “Git: new feature suggestion”
  1. Joao PintoJan 18, 2017
  2. Stefan BellerJan 18, 2017
  3. Joao PintoJan 18, 2017
  4. Konstantin KhomoutovJan 19, 2017
  5. Junio C HamanoJan 19, 2017
  6. Joao PintoJan 19, 2017
  7. Linus TorvaldsJan 19, 2017
  8. Joao PintoJan 19, 2017
  9. Linus TorvaldsJan 19, 2017
  10. Joao PintoJan 19, 2017
  11. Stefan BellerJan 19, 2017
  12. Joao PintoJan 20, 2017
  13. Jakub NarębskiJan 19, 2017
  14. Linus TorvaldsJan 20, 2017
  15. Jakub NarębskiJan 20, 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.