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

Re: Finally implement "git log --follow"

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Jun 21, 2007, 06:21 UTC
Message-ID
<e5bfff550706202321t354ec0e3xb218f382f1c983ae@mail.gmail.com>
In-Reply-To
<alpine.LFD.0.98.0706200940000.3593@woody.linux-foundation.org>
On 6/20/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
Show 5 quoted lines
>
> That said, you really would be better off using
>
>         git blame -M --incremental
>
That's how it is currently inplemented in qgit:
- Main view revision list + graph: git-rev-list
- File history and annotation: git-rev-list
The possible options are:

ALL GIT LOG -------------------

- Main view revision list + graph: git-log
- File history and annotation: git-log
Good: easy implementation and a lot of common code to share among
modules, all the current features (see "range fltering" below) are
preserved
Bad: Currently git-log does not support --stdin option, required IMHO
when git-log is runned by a tool, not a user, due to the possibility
of a very long command line.

MIXED ---------

- Main view revision list + graph: git-rev-list
- File history and annotation: git-blame
Good: Gain additional features of git-blame against git-log
Bad: FWIK "git blame -M --incremental" does not support annotating all
the files in history in one go, as it is possible both with
git-rev-list and git-log. You have to re-annotate the new file when
browsing file history with the mouse.

Impementation cannot reuse big chunks of code, so a lot of new code is needed and probably old one will not disappear.

FWIK "git blame -M --incremental" does not support "code lines range filtering", when with the mouse you select some lines of code and after filtering you see the subset of file's history that modified that range of code. This feature is currently supported by qgit annotating code.

Also jump to the same currently selected code line when switching to a different version in file history it is currently supported by annotate code.

INTERESTING --------------------

- Main view revision list + graph: git-log
- File history and annotation: git-blame
A curious mix.
Some advice?

Thanks Marco

Previous: Linus TorvaldsNext: Linus Torvalds
Message 6 of 11 in “Finally implement "git log --follow"”
  1. Linus TorvaldsJun 19, 2007
  2. Linus TorvaldsJun 19, 2007
  3. Marco CostalbaJul 4, 2007
  4. Marco CostalbaJun 20, 2007
  5. Linus TorvaldsJun 20, 2007
  6. Marco CostalbaJun 21, 2007
  7. Linus TorvaldsJun 21, 2007
  8. Johannes SchindelinJun 21, 2007
  9. Linus TorvaldsJun 21, 2007
  10. Linus TorvaldsJun 21, 2007
  11. Junio C HamanoJun 21, 2007

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.