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

Re: Adding Git to Better SCM Initiative : Comparison

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Jan 13, 2008, 15:16 UTC
Message-ID
<vpqd4s5ycvv.fsf@bauges.imag.fr>
In-Reply-To
<20080113150541.21883.qmail@science.horizon.com>
linux@horizon.com writes:
> "Rename support" is a kludge to make a fundamentally broken model
> less painful.
It's not.

Git _has_ rename support. Look into the code, you'll find some code whose purpose is to manage renames. And _no_, rename support is not just a direct consequence of commits being atomic.

Atomic commit help, but if you do nothing else, moving a file and then trying to merge will fail for example. So, in addition to atomic commits, you have at least 3 options : explicit file ID (bzr), recording renames (hg), or detecting renames after-the-fact (git).

-- 
Matthieu
Previous: linux@horizon.comNext: Jakub Narebski
Message 2 of 5 in “Re: Adding Git to Better SCM Initiative : Comparison”
  1. linux@horizon.comJan 13, 2008
  2. Matthieu MoyJan 13, 2008
  3. Jakub NarebskiJan 13, 2008
  4. linux@horizon.comJan 13, 2008
  5. linux@horizon.comJan 13, 2008

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.