On Thu, Jan 03, 2013 at 10:10:31PM +0100, Marc Hoersken wrote:
> 2013/1/3 Marc Hoersken <info_at_marc-hoersken.de>:
> > 2013/1/3 Marc Hoersken <info_at_marc-hoersken.de>:
> >> I haven't tested this myself, but from my experience with previous
> >> renames, GitHub and all the other tools in the git ecosystem will show
> >> you the history till the last rename, but won't automatically follow
> >> the history before that point.
> >
> > I have to correct myself on this one. It looks like recent versions of
> > git(-log) and gitk follow the history even before renames, but the
> > fact that the file was renamed is not visible to the user. gitk and
> > git log -p just display the new filename in the diffs for revisions
> > before the renaming. Besides the commit message there is no indication
> > that the file was renamed.
>
> Just ignore this amendment. I came to this conclusion by testing a
> file that wasn't actually renamed during these changes:
> lib/curl_schannel.c.
>
> Doing gitk --all and git log -p with lib/curl_ssluse.c proves my
> original point that history is not shown before the rename and the
> commit looks like an initial commit with git add.
>
> Tested using git version 1.8.0.msysgit.0
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html

Take a look at git log --follow. Git will gladly show you history
through renames:

$ git log --pretty=oneline lib/curl_file.c | wc -l
1

$ git log --follow --pretty=oneline lib/curl_file.c | wc -l
147

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-01-03