Re: Subversion != your filesystem (was mv != (cp && rm))

Florin Iucha wrote:

>On Wed, Nov 28, 2001 at 03:55:05AM +0100, Branko �ibej wrote:
>
>>Once we implement "svn ln" (which means a third kind of node, a
>>"reference", will appear in the filesystem), we'll have to be careful to
>>preserve the semantics of reference nodes within a copy. But that's
>>trivial -- reference nodes will behave exactly like C pointers: a copy
>>creates a new node, but its value (the node it refers to) remains the same.
>>
>
>What will happen if I link A to B and then
> 1. cp B C && rm B
> 2. mv B C
>
Don't know. :-)
The design for "svn ln" is far from complete. It hasn't even been
started yet, AFAIK.

>You can argue that in both cases A will link to C
>
Possibly.

> but, then what happens
>when
> cp B C && change C && cp B D && change D && rm B && commit
>where does A point to now?
>
This is not a move. A would be a dangling reference in this case.

-- 
Brane �ibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org