From: Aaron Gray <angray@beeb.net>
Date: Sun, 19 Aug 2007 19:17:31 GMT
Subject: Re: renaming question
Message-ID: <03bd01c7e295$976a2970$0600a8c0@ze4427wm>
In-Reply-To: <85sl6fqr9n.fsf@lola.goethe.zz>

> "Aaron Gray" <angray@beeb.net> writes:
>
>>>* Aaron Gray:
>>>
>>>> I have a very large C source project that I am converting from C to 
>>>> C++.
>>>>
>>>> Is it posssible to track changes with renamed files in GIT ?
>>>
>>> You don't need to rename the files if you compile them using g++.  If
>>> you still want to rename them, most history-related GIT commands
>>> accept an -M switch which enables rename ("move") detection.
>>
>> For sanity they have to be renamed.
>>
>> I am a bit of a GIT newbie. With the -M switch what would be the
>> proceedure with a single file conversion such as with test.c and
>> test.cpp ?
>>
>> Would the following do the trick ?
>>
>>    git add test.c
>>    git commit
>>
>>    rename test.c test.cpp *
>>    vi test.cpp
>>
>>    git rm test.c
>>    git add test.cpp
>>    git commit -M
>>
>> Many thanks in advance,
>
> There is no such thing as "git commit -M".  git does not keep track of
> renames.  It generates the rename info on the fly when you ask it for
> patches, log stats, blame annotations or similar.

Could you elaborate maybe with a rough example for generating patches.

Aaron