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

Re: exit codes and locking

From: Jim Correia <jim.correia_at_pobox.com>
Date: 2005-04-08 19:38:59 CEST

On Apr 8, 2005, at 1:27 PM, Julian Foad wrote:

>> 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.
> Bug. Thanks for reporting it.

Should I file it in the issue tracker?

>> 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?
> Hmm... svn is not very good at responding to files that do not exist
> (neither on disk nor in version control) - it tends to ignore them as
> if you hadn't mentioned them. I think that's what's happening here
> ("OK, I've removed any files you asked me to - which wasn't any at
> all"). Likewise "svn up foo" and "svn st foo" silently succeed even
> if "foo" is nonexistent and unknown. I regard those all as bugs. I
> don't know if they are all filed in the issue tracker.

Should I file a bug against the rm case in the issue tracker, or not?

What happens if I do

svn rm foo bar

and foo exists, but bar does not? What should it return in that case?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 19:40:02 2005

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