From: Jakub Narebski <jnareb@gmail.com>
To: James Blackburn <jamesblackburn@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log --follow doesn't follow a rename over a merge
Date: Thu, 16 Jun 2011 06:25:19 -0700 (PDT) [thread overview]
Message-ID: <m362o5vrhd.fsf@localhost.localdomain> (raw)
In-Reply-To: <BANLkTimjEp0ntq80qttT9uZN2YGuhsnZBw@mail.gmail.com>
James Blackburn <jamesblackburn@gmail.com> writes:
> I'm trying, without success, to get git log to show the history of a
> file across a rename. I'm using git version 1.7.5.4, and git blame
> has no such issues tracking the source of the lines.
[...]
> Have I done something wrong in grafting history like this, or is this
> just a problem with the way git log --follow tracks renames?
The `--follow` option to git-log is more of a bolted-on hack rather
than proper solution, see 750f7b6 (Finally implement "git log
--follow", 2007-06-19), and it might not work in all cases.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-06-16 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 22:41 git log --follow doesn't follow a rename over a merge James Blackburn
2011-06-16 13:25 ` Jakub Narebski [this message]
2011-06-16 13:31 ` James Blackburn
2011-06-16 17:01 ` James Blackburn
2011-06-16 17:45 ` Jeff King
2011-06-16 17:34 ` Jeff King
2011-06-16 17:59 ` Junio C Hamano
2011-06-16 18:15 ` Jeff King
2011-06-16 19:41 ` James Blackburn
2011-06-16 18:41 ` James Blackburn
2011-06-16 19:36 ` Junio C Hamano
2011-06-16 21:29 ` James Blackburn
2011-06-16 22:14 ` James Blackburn
2011-06-16 18:21 ` James Blackburn
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=m362o5vrhd.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jamesblackburn@gmail.com \
/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