git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: git log --follow <filename> doesn't follow across 'subtree strategy' merge
Date: Sun, 22 Jun 2008 14:51:49 +0200	[thread overview]
Message-ID: <200806221451.50624.jnareb@gmail.com> (raw)

When trying to see all history of gitweb using

  $ git log -C -C --raw --abbrev --follow gitweb/gitweb.perl

I have noticed that while it correctly detects renaming 
gitweb/gitweb.cgi to gitweb/gitweb.perl, and follows this rename, it 
cannot get past merge commit 0a8f4f0020cb35095005852c0797f0b90e9ebb74
and follow moving gitweb.cgi to gitweb/gitweb.cgi.

To get full history I have to use

  $ git log -C -C --raw -- gitweb/gitweb.perl gitweb/gitweb.cgi \
                           gitweb.cgi

Adding '--full-history' doesn't help...
-- 
Jakub Narebski
Thorn, Poland
ShadeHawk on #git

                 reply	other threads:[~2008-06-22 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200806221451.50624.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.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).