From: Jeff King <peff@peff.net>
To: Gregg Leichtman <gslaccts@verizon.net>
Cc: git@vger.kernel.org
Subject: Re: git log over restricts output when using --follow?
Date: Thu, 9 Sep 2010 15:51:59 -0400 [thread overview]
Message-ID: <20100909195159.GC1146@sigill.intra.peff.net> (raw)
In-Reply-To: <4C86D5AE.6030302@verizon.net>
On Tue, Sep 07, 2010 at 08:15:42PM -0400, Gregg Leichtman wrote:
> (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
prev parent reply other threads:[~2010-09-09 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 0:15 git log over restricts output when using --follow? Gregg Leichtman
2010-09-09 19:51 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100909195159.GC1146@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gslaccts@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).