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

Re: git blame --follow

From
Jeff King <peff@peff.net>
Date
Sep 6, 2012, 09:58 UTC
Message-ID
<20120906095804.GA15277@sigill.intra.peff.net>
In-Reply-To
<k29hpo$3av$1@ger.gmane.org>
On Thu, Sep 06, 2012 at 09:02:17AM +0200, norbert.nemec wrote:
Show 5 quoted lines
> 'git blame --follow' seems to be undocumented. The exact behavior is
> not clear to me. Perhaps an alias for some combination of '-C' and
> '-M'? It seems not be be fully consistent with 'git log --follow'.
> 
> Could someone clarify? Did I miss something?

I don't think it was ever intended to do anything; the only reason it is not rejected outright is that "blame" piggy-backs on the regular revision option parser used by "log" and others.

What would you expect it to do?

I can't think of a sane behavior for "blame --follow". The follow code is about tweaking path-limiting during traversal, but blame does not use pathspecs. It tracks content, and the "-C" option already instructs it to look across file boundaries.

-Peff
Previous: norbert.nemecNext: norbert.nemec
Message 2 of 15 in “git blame --follow”
  1. norbert.nemecSep 6, 2012
  2. Jeff KingSep 6, 2012
  3. norbert.nemecSep 6, 2012
  4. Jeff KingSep 6, 2012
  5. Documentation/git-blame.txt: --follow is a NO-OPDrew Northup, Sep 19, 2012
  6. Junio C HamanoSep 19, 2012
  7. Jeff KingSep 19, 2012
  8. Junio C HamanoSep 19, 2012
  9. Jeff KingSep 19, 2012
  10. Kevin BallardSep 19, 2012
  11. Jeff KingSep 19, 2012
  12. Kevin BallardSep 19, 2012
  13. Re* [PATCH] Documentation/git-blame.txt: --follow is a NO-OPJunio C Hamano, Sep 21, 2012
  14. Junio C HamanoSep 21, 2012
  15. Junio C HamanoSep 20, 2012

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.