Re: svn status -v on nonexistent files has changed

Martin Pool <mbp@samba.org> writes:
> I'm running Subversion 0.23 from Debian.
>
> The behaviour of "svn status -v" on a nonexistent file seems to have
> changed in the last couple of releases.
>
> This breaks vc-svn, and as a result it is not possible in emacs to
> open a new file in a svn-controlled directory, which is an annoying
> failure.

I couldn't reproduce this with head (rev 6163) of vc-svn.el and of
Subversion. I think 'svn status' has already been fixed back.

> For example:
>
> $ ls -la
> total 12
> drwxr-sr-x 3 mbp mbp 4096 Jun 6 14:08 .
> drwxr-sr-x 4 mbp mbp 4096 Jan 7 15:44 ..
> drwxr-sr-x 8 mbp mbp 4096 Jun 6 14:09 .svn
> $ svn st nothere
> $ svn st -v nothere
> $ echo $?
> 0
> $ svn st -vu nothere
> svn: Can't find an entry
> svn: svn_wc_is_wc_root: 'nothere' is not a versioned resource

In 6163, Subversion behaves like this

   $ svn st -vu nothere
   $

...which vc-svn.el handles just fine.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 6 17:11:32 2003