Re: git log --follow doesn't follow a rename over a merge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]