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

exit codes and locking

From: Jim Correia <jim.correia_at_pobox.com>
Date: 2005-04-08 18:09:53 CEST

Is (our should) subversion be consistent about returning non-zero exit
codes when an operation failed?

If I attempt to do a commit in a working copy of a file locked in
another working copy, the commit fails with an error message, and the
exit code is 1.

If I attempt to unlock a file which is locked in another working copy,
without --force, it fails with an error message and the exit code is 1.

However, if I attempt to lock a file that is locked in another working
copy, it fails with an error message, but the exit code is 0.

This is using the 1.2rc1 tarball.

===

I picked rm as another random operation to try:

correia$ svn rm someFileThatDoesNotExist
correia$ echo $?
0
Is that as it should be, or should it complain that the file doesn't
exist?

Jim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 18:11:14 2005

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