Re: Out of date errors just after a revert

Marc Haisenko wrote:

>
> You should have done "svn revert foo" instead of "svn revert ."
>
Thanks for your hint. That does the job, but only if I remove foo/bar
from my WC before. If I just do the following I get an working copy not
locked:
---SNIP---
D:\TESTPR~1\xxx>svn add foo
A foo
A foo\bar

D:\TESTPR~1\xxx>svn revert foo
svn: Working copy 'foo/bar' not locked

D:\TESTPR~1\xxx>svn st
A foo
A foo\bar
---SNIP---

Now is that logical?

if I 'svn del foobar' and find out that I made a mistake, I have to 'svn
revert .', which is logical, since 'foobar' is no longer visible to me
and it's an operation on foobars parent folder.

if I 'svn add foobar' and find out that I made a mistake, I have to 'svn
revert foobar', which doesn't even do the job without me moving away
foobar first?!?
This is not logical to me, because I'd expect 'svn revert .' to restore
my current folder to its original condition.

Cheers
- Lübbe

--
       ___
  oo  // \\      TortoiseSVN
(_,\/ \_/ \     The coolest Interface to (Sub)Version Control
   \ \_/_\_/>    http://tortoisesvn.tigris.org
   /_/   \_\
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org