From: James Blackburn <jamesblackburn@gmail.com>
Date: Thu, 16 Jun 2011 17:01:25 GMT
Subject: Re: git log --follow doesn't follow a rename over a merge
Message-ID: <BANLkTi=4S08h=uMV5oo7S9qpruMot2kVfg@mail.gmail.com>
In-Reply-To: <BANLkTik1-UvEXqzgdXwcK3x6_o8fDiwB7g@mail.gmail.com>

I see a lot of this has been discussed before... but just to add that
Jeff's blame-log.sh:
http://git.661346.n2.nabble.com/alternate-log-follow-idea-td1385917.html
seems to work and show the full history of the file past the rename+merge!

I was also interested in whether there's a better way of re-connecting
history than grafting one repository's history into the commit which
made it visible in another?  AFAICS the graft is no different to a
merge commit which contains a rename in the merged node, so I'm
guessing this is a reasonable thing to do?

Cheers,
James