Switch from SVN to xxx ?

[Teemu Likonen]

* 2010-06-03 21:44 (+0200), Jelmer Vernooij wrote:

> On Thu, 2010-06-03 at 21:16 +0300, Teemu Likonen wrote:
>> http://thread.gmane.org/gmane.comp.version-control.git/94861/focus=94964

>> In short, "git log --follow" does not even have that feature, so it's
>> wrong to say that Git "gave up".

> My message doesn't mention --follow.

Right, but the other Samba guy (Kai Blin) and the Git people on the
linked discussion did mention it. The reason they mentioned it is
because "git log --follow" is related to what you wanted to achieve.
"git log" alone doesn't follow through renames at all (and never will, I
dare to say).

Here's the main point why I replied to your message: You have said that
Git couldn't do what you wanted and you presumed that it's because the
rename was too big. My correction is that the reason is not the size of
rename.

>>     git log -C -p -- old/dir new/sub/dir

> The whole point is that the VCS remembers the old names of a file for
> you so that it can follow the history of that file. If it requires you
> to remember all the different filenames under which a file existed,
> then how is that rename support? Both Bazaar and Mercurial will
> display history across the rename when you ask for the log of a file.
> Git doesn't, at least not in all situations.

Hey, of course you can say that Git is suboptimal because there is no
intelligent directory-level "--follow". I have no problem with you
saying that. Then to your question "how is that rename support." In
command like

    git log -C -p -- old/dir/ new/dir/

there is rename support in diffs: it shows the diff (if any) between
revisions of all individual, possibly renamed, files as well as the
similarity-%.