threads / discuss / 25110

Strange log results

Subject: Strange log results

## tl;dr

One message between Sep 15, 2010 and Sep 15, 2010.

replies: 0people: 1as markdown or json

Torgny Nyblom· Sep 15, 2010, 18:02 UTC · lore
Hi,

I'm working on converting the KDE subversion repository to git, as a part of this I'm trying to validate that the conversion hasn't missed any revisions or merges but when I run "git log" with different options I get (in my mind) strange results.

git log <file> -> produces a list of commits git log --follow <file> -> produces an empty list (no output) git log --name-status <file> -> no info about file

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.

Is there any legit situation where this might happen? If so what? If not is this a bug in my convert program or in git?

/Regards Torgny

← back to recent threads