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

Re: git log over restricts output when using --follow?

From
Jeff King <peff@peff.net>
Date
Sep 9, 2010, 19:51 UTC
Message-ID
<20100909195159.GC1146@sigill.intra.peff.net>
In-Reply-To
<4C86D5AE.6030302@verizon.net>
On Tue, Sep 07, 2010 at 08:15:42PM -0400, Gregg Leichtman wrote:
Show 14 quoted lines
> (3)
> 
> |gsl@aragorn:~/gitTest> gitnp log -2 --follow --pretty=oneline junk.txt
> 500e8791578c5baf7a139d4997841769a995ac6b mod of junk and junk3
> |
> 
> (4)
> 
> |gsl@aragorn:~/gitTest> gitnp log -2 --pretty=oneline junk.txt
> 500e8791578c5baf7a139d4997841769a995ac6b mod of junk and junk3
> 594ceed7a0fb35a860a6e2cb913d5398f09a861f 1st mod junk.txt
> |
> 
> Why don't I see 2 output lines for item (3) above?

Without looking closer into the problem, I would guess that it is because of the hack-ish way that --follow is implemented. That is, most history pruning and simplification happens outside of the actual --follow traversal. So yes, it looks like a defect, but fixing it may involve rewriting --follow entirely.

But don't let that discourage you from looking further. :)
-Peff
Previous: Gregg Leichtman
Message 2 of 2 in “git log over restricts output when using --follow?”
  1. Gregg LeichtmanSep 8, 2010
  2. Jeff KingSep 9, 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.