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

Is there a "--follow" equvalent argument to git-rev-list?

From
SBSteinar Bang <sb@dod.no>
Date
Nov 28, 2011, 10:37 UTC
Message-ID
<87vcq4zg6p.fsf@dod.no>

I'm trying to make emacs vc log (`C-x v l') show the full history of git versioned files.

In my first attempt, I tried adding a "--follow" argument to "git log" in the vc-git-print-log message. This made `C-x v l' show the full log.

But the problem with this solution was that commands done from the log,
such as diffing (a very convenient way to do diffs, when the "version
numbers" are sha1 hashes...), showing a particular revision, or
annotating from that revision and back, didn't work.  See the comment at
the end of this bug:
 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8756

Today I decided to take another peek at this, but vc-git.el in the emacs 23.1 version of the file, now uses "git rev-list" instead of "git log" to get the revision list.

And "git rev-list" doesn't seem to have anything similar to "--follow"...? At least I haven't found it.

The man page doesn't contain the text "renam".

Guessing at what the man page has meant, I've tried adding the "--all" and "--full-history" arguments, but `C-x v l' still only shows history back to the last move.

Is there an argument to "git rev-list" that will make it track across renames? Or is this only possible with "git log --follow"?

Thanks!
- Steinar
Next: Junio C Hamano
Message 1 of 2 in “Is there a "--follow" equvalent argument to git-rev-list?”
  1. Steinar BangNov 28, 2011
  2. Junio C HamanoNov 28, 2011

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.