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

Re: Handling failures

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-19 14:07:02 CEST

"Paramjit Oberoi" <p_s_oberoi@hotmail.com> writes:

> * If a checkout fails (for instance, because of an incorrectly
> specified path),
> no new files/directories should be created. For instance, if I do:
> svn co file:///svn-repository/my-cool-projcet/module1
> (and the repository does not contain "my-cool-projcet") an empty directory
> called "module1" is created with a .svn subdirectory. So I cannot simply
> reissue the checkout command with the corrected spelling---I must first
> delete the bogus directory, otherwise subversion complains that the
> "module1" directory is already a working copy for a different path.

This is fixed in HEAD.

> * Accessing a remote repository via ra_svn should check if the same
> subversion version is installed on both ends;

While svn is in alpha, we have a release-interoperability policy (and

But in general, I agree: I wish that both of our network layers were
able to *either* negotiate svn release number or protocol version.
It's been discussed on this list, but nothing concrete has come out of

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 19 14:09:26 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.