From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date: Wed, 22 Sep 2010 08:05:51 GMT
Subject: Re: git log broken?
Message-ID: <vpqk4mecie8.fsf@bauges.imag.fr>
In-Reply-To: <20100922094808.07be1757@explosive.nyblom.org>

Torgny Nyblom <kde@nyblom.org> writes:

> It seems like this occurs when there is a merge only commit as the
> first commit in the list returned by the "bare" log command.

"git log --follow" is not the best part of Git :-( (especially
compared to "git blame", which is excellent at following the history
of lines of code).

There were some discussion already on --follow having bad behavior on
merge commit, like:

  http://thread.gmane.org/gmane.comp.version-control.git/151502/focus=151664

But no one is really investing energy to make "git log --follow" what
it should really be, AFAIK.

> If not is this a bug in my convert program or in git?

Your converter cannot have "mis-imported" renames, since renames do
not appear in the repository with Git.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/