Re: suggestions for neater operation ...

> 1. svn mkdir bla/bla
> should create both directories.
> the user wants it, so why print an error message and
> force the user to do svn mkdir bla, and svn mkdir
> bla/bla
> (i know, it is the unix behaviour ... and not the
> windows one,
> but that should not be a reason ;) )

I agree with this. IMO, default behavior should be recursive (it is for
"svn delete dir/"), and allow the nonrecursive option.

> 7. svn up:
> should be save for some unwise person deleting the
> ".svn".
> not stop with "./dir is not a working copy
> directory",
> but restore the .svn.

You are asking the impossible here. How can you rebuild the .svn
directory, when not having it means you know nothing about where a
working copy came from or what revision it is at? That's like asking for
something from nothing If you (since you are comparing a lot to existing
tools) "rm -rf CVS/", you have the same problem. It's even worse for
SVN, mainly because SVN has much more metadata stored in that directory.

Moral, don't delete the .svn directory.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://linux1394.sourceforge.net/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org