>> svn up -r42
>>
>> will update your working copy to the state of the repository at
>> revision 42.
>>
>>
>> Something different: If you want to undo a change, and commit that
>> undo to the repository, you do a reverse merge, which is described
>> in the book:
>>
>> http://svnbook.red-bean.com/en/1.2/>> svn.branchmerge.commonuses.html#svn.branchmerge.commonuses.undo
>>
>
> I'm just chiming in here because after seeing the last response, I
> jumped
> the gun and attempted to test using the command 'svn up -r##'.
>
> This worked OK. I did this on a subdirectory of my working copy.
>
>
> % svn up -r102 subdir1
> D subdir1
>
> I happened to have picked a revision which did not have this
> directory.

I assume your working copy also happened to have local modifications
to it. Therefore, Subversion did not delete the directory.

> Then for kicks I tried doing a regular update at the top-level of the
> working copy:
>
> % svn up
> svn: Failed to add directory 'subdir1': object of the same name
> already
> exists

Correct: Subversion will not add an item if one of the same name is
already there.

If subdir1 contained local modifications, rescue them, then delete
the directory. Then you can "svn up" back to the HEAD revision.

--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org