git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Santiago Gala <sgala@apache.org>
Cc: git@vger.kernel.org
Subject: Re: BUG:git-log --follow <path> should never trim output WRT equivalent git-log <path>
Date: Mon, 24 Mar 2008 21:45:04 -0400	[thread overview]
Message-ID: <20080325014504.GA15864@coredump.intra.peff.net> (raw)
In-Reply-To: <loom.20080324T161602-184@post.gmane.org>

On Mon, Mar 24, 2008 at 04:19:01PM +0000, Santiago Gala wrote:

> $ git log  -M -C -C --color --stat --follow -- gitk-git/po/de.po | wc -l
> 0
> sgala@marlow ~/newcode/git/git (master)$ git log  -M -C -C --color --stat --
> gitk-git/po/de.po | wc -l
> 31
> $ git --version
> git version 1.5.4.4
> 
> I find very strange that --follow makes git log to stop outputting the first
> entries.

I think the tricky thing here is that every one of those commits is a
merge, which doesn't actually "introduce" any content, and that probably
confuses the "--follow" code.

The thing is that getting the history of gitk-git specifically is a bit
tricky. All of the commits actually happen to, e.g., the file 'gitk' in
the main gitk repository, and then Junio merges it into git using a
special "subtree" merge as 'gitk-git/gitk'. So looking at a path in
'gitk-git' will always just turn up merge commits; the actual commits
took place on a different path.

But I haven't looked too closely at what's going on, so I may be way off
base. My two cents.

-Peff

      reply	other threads:[~2008-03-25  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 16:19 BUG:git-log --follow <path> should never trim output WRT equivalent git-log <path> Santiago Gala
2008-03-25  1:45 ` 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=20080325014504.GA15864@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=sgala@apache.org \
    /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).