On 4/23/2010 11:00 AM, Bob Archer wrote:
>> On 4/23/2010 10:49 AM, Bob Archer wrote:
>>>>
>>>>> Furthermore reverting the working copy does not work and updates skip
>>>>> the "folder" resource completely.
>>>>
>>>> You've deleted the pristine copy under .svn for that directory.
>> There's
>>>> no copy left to revert.
>>>
>>> Update is totally different than revert. If you delete the folder then
>> do an UP the folder is replaced "A". However, if you create a dir then
>> remove that and do an UP the folder isn't fetched. It does seem strange. I
>> assume something is going on where .svn at the root indicates that folder
>> is there.
>>>
>>
>> It seems wrong to remove an unmanaged item, although in the special case
>> of an empty directory I guess it wouldn't make much difference.
>>
> I agree it is wrong. But, I also think something is smarmy here. For example, if you create the folder after deleting it with the OS command (rather than SVN) then realize your mistake, rd the folder and do svn up it really should get the folder from the repo assuming your depth is set to infinity.
>
> If I do the same thing with a file... delete it (OS cmd), then create the same name, svn will report it with a status of "M" and a commit will merge the diff between that file and base.
That's not equivalent. Removing/replacing a file is just a local edit
of a managed item, and the same thing an editor program might do. The
equivalent would be removing the containing directory and thus the .svn
metadata, then putting back the directory and a new file of the same name.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-04-23 18:11:23 CEST