cURL / Mailing Lists / curl-library / Single Mail


Re: [bagder/curl] 13606b: build: make use of 93 lib/*.c renamed files

From: Marc Hoersken <>
Date: Thu, 3 Jan 2013 22:10:31 +0100

2013/1/3 Marc Hoersken <>:
> 2013/1/3 Marc Hoersken <>:
>> 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:

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:
Received on 2013-01-03