[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn status -v on nonexistent files has changed

From: Martin Pool <mbp_at_samba.org>
Date: 2003-06-06 06:14:35 CEST


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

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 $?
$ svn st -vu nothere
svn: Can't find an entry
svn: svn_wc_is_wc_root: 'nothere' is not a versioned resource
$ touch notadded
$ svn st notadded
? notadded
$ svn st -v notadded
? notadded

Previously running 'svn st nothere' would produce an error message, or
at least say '?'. I think an error message is probably better.

I guess if you really wanted to keep this behaviour then vc-svn could
be patched to accomodate it. I couldn't see a changelog entry
indicating that it was intentional.

This looks like yet another variation on bug 1042, though it is not
the same as the previous one. (Reporting bugs in svn st seems to be
as far as I ever get with helping svn :-)

Please cc me on replies.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 6 06:15:49 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.