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

Re: [RFC] 'basic/additional command set' - adding svn subcommands without destroying our learning curve

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-11-02 22:51:29 CET

On Wed, 2005-11-02 at 13:01 +0000, Max Bowsher wrote:
> To break the deadlock between the opposing motivations of 'keep svn simple',
> and 'add useful utilities', I'd like to propose that we introduce the notion
> of a basic and an additional command set. Practically, all this means is
> splitting commands between `svn --help` and `svn --help-additional`, and
> dividing our documentation of commands in the same way.

We might give it a more descriptive name, like --help-utilities.

I could live with this, but we should come up with some pretty clear
criteria for separating basic commands from utilities. I'm not sure if
I can quite nail it down myself. Certainly, I think it should be
possible in principle to implement all utility operations in terms of
core operations, although our implementation might be more efficient.

To me, "import" and "export" should remain basic commands. import can
be done with co/add/commit, but it's not quite the same operation;
export can't be done at all without violating the abstraction barrier.

Some new command proposals would still have to be basic commands. For
instance, we've talked about having non-broken partial checkout support,
and making it possible to add or remove a subtree from a partial
checkout. The removal command can't be a utility command since there's
no way to do it terms of today's basic operations.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 2 22:52:25 2005

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