On Nov 1, 2007, at 1:27 AM, Greg Hudson wrote:
> 27 minutes in, we learn that git doesn't track explicit renames, but
> instead intuits them (as well as copies) from matching file contents.
>
> I assume that means if you're doing a tree reorg, you really want to
> commit the tree operations separately from any file modifications you
> want to do to the renamed files (e.g. because you're moving Java
> source
> and renaming the classes at the same time), or git won't be able to
> tell. That might in turn result in a temporarily broken build, but
> that's a minor point which you could easily plaster over with
> branches.
It doesn't actually totally hork up if you do a rename and an edit. My
friend that uses git for *everything* says that it uses a heuristic to
determine file ancestry across renames. Supposedly it works really
really well. I've not used git personally, so I can't offer much
commentary on how well this works in practice. What I've heard is that
they track renames and copies about as well as Subversion.
Augie
>> <snip>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 1 15:42:04 2007