From: Jakub Narebski <jnareb@gmail.com>
To: David Lang <david@lang.hm>
Cc: git@vger.kernel.org, "Alexey Mahotkin" <squadette@gmail.com>
Subject: Re: git documentation
Date: Mon, 05 Jan 2009 17:07:09 -0800 (PST) [thread overview]
Message-ID: <m33afxb5tw.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.10.0901051745280.28514@asgard.lang.hm>
David Lang <david@lang.hm> writes:
> 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
next prev parent reply other threads:[~2009-01-06 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 1:46 git documentation david
2009-01-06 1:07 ` Jakub Narebski [this message]
2009-01-06 1:46 ` Miklos Vajna
-- strict thread matches above, loose matches on Subject: below --
2008-07-22 3:35 Git Documentation Scott Chacon
2008-07-22 7:17 ` Johan Herland
2008-07-22 7:56 ` david
2008-07-22 9:21 ` Johan Herland
2008-07-22 11:40 ` Johannes Schindelin
2008-07-22 14:46 ` Scott Chacon
2008-07-22 15:47 ` Jay Soffian
2008-07-22 16:07 ` Johannes Schindelin
2008-07-22 10:15 ` Pedro Melo
2008-07-24 0:31 ` Karl Hasselström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33afxb5tw.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=squadette@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.