Re: Backing out changes: the prefered method?

Sean Russell <ser@germane-software.com> writes:

> ser@maus ~% svnadmin create repos
> ser_at_maus ~% svn co file:///home/ser/repos/ -d wc
> ser@maus ~% cd wc
> ser@maus ~/wc% mkdir A
> ser@maus ~/wc% echo foo > A/b
> ser@maus ~/wc% svn add A A/b
> A A
> A A/b
> ser@maus ~/wc% svn ci
> Adding /home/ser/wc/A
> Adding /home/ser/wc/A/b
> Committed revision 1.
> ser@maus ~/wc% svn up
> ser@maus ~/wc% svn mv A B
> A B
> D A/b
> D A
> ser@maus ~/wc% svn ci
> Deleting /home/ser/wc/A
> Adding /home/ser/wc/B
> Committed revision 2.
> ser@maus ~/wc% svn up
> D ./A
> ser@maus ~/wc% echo bar >> B/b
> ser@maus ~/wc% svn ci
> Sending /home/ser/wc/B/b
> Committed revision 3.
> ser@maus ~/wc% svn up
> ser@maus ~/wc% svn diff -r1 B/b
>
> svn_error: #21054 : <Filesystem has no such file>
> file not found: filesystem `/home/ser/repos/db', revision `1', path `/B'

I can argue that the error message is strictly correct, there is no
revision 1 of "B/b" :)

Yes, it probably should do something more. This problem affects other
commands as well, 'svn up' and 'svn cp' for example. It is a variant
of issue #581.

-- 
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org