git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git log broken?

From
TNTorgny Nyblom <kde@nyblom.org>
Date
Sep 22, 2010, 07:48 UTC
Message-ID
<20100922094808.07be1757@explosive.nyblom.org>
Hi,

(Resend as it got no replies and I want to be sure that is wasn't lost in the noise)

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

Next: Matthieu Moy
Message 1 of 3 in “git log broken?”
  1. Torgny NyblomSep 22, 2010
  2. Matthieu MoySep 22, 2010
  3. Michael J GruberSep 22, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.