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

Re: git documentation

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 6, 2009, 01:07 UTC
Message-ID
<m33afxb5tw.fsf@localhost.localdomain>
In-Reply-To
<alpine.DEB.1.10.0901051745280.28514@asgard.lang.hm>
David Lang <david@lang.hm> writes:
Show 10 quoted lines
> On lwn there is a comment (under the GNOME survey topic)
> http://lwn.net/Articles/313435/
> 
> The Shlomi Fish "Better SCM" site for example is very clear that Git
> won't do a merge across a rename. It even has a citation for this
> claim. But as a Git user who has actually done a merge across a rename
> I know it works just fine, and anyone familiar with Git's internals
> will guess immediately why. Yet probably there is no line of
> documentation on the Git site or elsewhere that I can quote to justify
> adding a "Yes" to the comparison.

I have tried to add info about Git to Better SCM quite a long time ago; it was finally added by (IIRC) Alexey Mahotkin for http://versioncontrolblog.com and sent for inclusion in Better SCM to Shlomi Fish.

Unfortunately it contains some factual errors. I have sent corrections
to Alexey, but didn't finish it:
  "Git at Better SCM Initiative comparison of VCS (long)"
  http://article.gmane.org/gmane.comp.version-control.git/97253
(see also other posts in this thread, and other posts with the same,
or similar, subject on git mailing list).
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: david@lang.hmNext: Miklos Vajna
Message 2 of 3 in “git documentation”
  1. david@lang.hmJan 6, 2009
  2. Jakub NarebskiJan 6, 2009
  3. Miklos VajnaJan 6, 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.