{"thread":{"id":"25110","subject":"Strange log results","startedAt":"2010-09-15T18:02:03Z","lastAt":"2010-09-15T18:02:03Z","messageCount":1,"participants":["Torgny Nyblom"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"150743","messageId":"20100915200203.754a312f@explosive.nyblom.org","threadId":"25110","inReplyTo":null,"subject":"Strange log results","fromName":"Torgny Nyblom","fromEmail":"kde@nyblom.org","sentAt":"2010-09-15T18:02:03Z","receivedAt":"2010-09-15T18:02:03Z","isPatch":false,"sender":{"key":"kde@nyblom.org","avatar":null},"body":"Hi,\n\nI'm working on converting the KDE subversion repository to git, as\na part of this I'm trying to validate that the conversion hasn't missed\nany revisions or merges but when I run \"git log\" with different options\nI get (in my mind) strange results.\n\ngit log <file> -> produces a list of commits\ngit log --follow <file> -> produces an empty list (no output)\ngit log --name-status <file> -> no info about file\n\nIt seems like this occurs when there is a merge only commit as the\nfirst commit in the list returned by the \"bare\" log command.\n\nIs there any legit situation where this might happen?\nIf so what?\nIf not is this a bug in my convert program or in git?\n\n/Regards\nTorgny\n"}]}