FWIW, it still behaves this way in 1.7: % $svn up foo Skipped 'foo' Summary of conflicts: Skipped paths: 1 % $svn st file svn: warning: W155007: '/home/daniel/file' is not a working copy %
with an exit code of 0 in both cases. I do think there were other improvements to the cmdline client's exit codes consistency and error handling in general, see dev@ archives (or try 1.7.0-alpha1). Vincent Lefevre wrote on Sun, Jun 12, 2011 at 03:51:34 +0200: > The exit status of svn commands doesn't seem to be specified, > at least not by "svn help <subcommand>". > > In particular, "svn update <file>" and "svn status <file>" seem > to always return with a 0 exit status on non-existing files. > This may be normal for "svn update" in a working copy, because > the command makes sense in case the file was added. Ditto for > "svn status": the user may want to test whether the file is in > base but has been removed with "rm", for instance. But I wonder > whether the 0 exit status is correct when not in a working copy. > > There has already been a too short discussion about this: > > http://svn.haxx.se/users/archive-2006-03/0918.shtml > > and there doesn't seem to be an entry in the issue tracker. > > -- > Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
