Torgny Nyblom <kde@xxxxxxxxxx> 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/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html