svn status handling uncontrolled and non-existant files

Unexpected behaviours of svn status:

- Verbose mode and recursive mode both list uncontrolled files, but do
not list uncontrolled directories.

- When explicitly given the name of an uncontrolled file, it lists its
status as ?, as expected.

- When explicitly given the name of an uncontrolled directory, it fails
and exits without continuing the report:

julianfoad@linux:~/src/subversion svn status *
A A_NEW_DIR
        BUGS
        CHANGES
        COMMITTERS
        COPYING
        HACKING
        IDEAS
        INSTALL
? Makefile
        Makefile.in
        PORTING
        README
subversion/libsvn_wc/status.c:718: (apr_err=155007)
svn: Path is not a working copy directory
svn: svn_wc_statuses: apr is not a working copy directory

- When explicitly given the name of a non-existent file or directory, it
implies that the file exists and matches the repository:

julianfoad@linux:~/src/subversion ls blah
ls: blah: No such file or directory
julianfoad@linux:~/src/subversion svn status blah
        blah
julianfoad@linux:~/src/subversion svn status blah/
        blah
julianfoad@linux:~/src/subversion svn status blah/blah
subversion/libsvn_wc/lock.c:289: (apr_err=155006)
svn: Invalid lock
svn: lock path is not a directory (blah)
julianfoad@linux:~/src/subversion

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:18:45 2006