kfogel@collab.net wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
>> Here's an example:
>>
>> When you run 'svn rm foo; svn commit':
>>
>> 1. a new repos revision is created where foo is gone, say, rev N.
>> 2. foo is (effectively) removed from your .svn/entries file
>> 3. the working parent-dir of foo is still at rev N-1.
>>
>> Technically, your working parent-dir is "out of sync" with reality: it
>> claims to be at rev N-1, yet it's missing foo. But, when you run 'svn
>> copy working-copy URL', a pristine version of the parent directory is
>> used to build the server-transaction. The file seems to magically
>> reappear in the transaction, and the URL doesn't look like a perfect
>> reflection of your working-copy anymore.
>>
>> I'm not sure if this is a bug or not. :-)
>
> This is a bug, but are you absolutely sure it's true?
>
> The *whole purpose* of supporting 'svn cp working-copy URL' is to be
> able to preserve snapshots of working copy states, for example, to
> reproduce a bug. If it doesn't preserve the fact that an item is
> missing, then that's a bug.
Bug 1802, to be precise.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 26 19:28:13 2004