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

Re: git log broken?

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Sep 22, 2010, 08:05 UTC
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/
Previous: Torgny NyblomNext: Michael J Gruber
Message 2 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.