Re: suggestions for neater operation ...

On 4/8/02 9:36 PM, "solo turn" <soloturn99@yahoo.com> wrote:

> 1. svn mkdir bla/bla
> should create both directories.

okie

> 2. svn mv myentry bla/myentry
> same reason as in 1

Don't like this one. In the above case I think it is more likely that the
user wanted to create both dirs. In this case I think it more likely that
the user mistyped the directory name.

> 3. svn add mydir
> mydir contains a lot of files, intention was to add
> the directory with contents

> --> throw away the -R and make recursive he default

Sounds reasonable.

> --> have a -N flag if somebody really just wants to
> add the directory
> (as with svn status)

Okie, (although you could also just let people use mkdir in that case)

> --> maybe also understand "svn add *"

Um, isn't this a shell function?

> 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.

As Ben said, this is impossible at the top level of a working copy. It
might be nice if the .svn dirs were re-added at lower levels in the
hierarchy though. E.g. If I type `svn up` in a working copy, and
./subdir/.svn is missing, then that dir could be re-build. I think this is
related to issue #714. And will probably get a similar priority.

Later,

\x/ill :-}

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 5 05:52:07 2002