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

Re: svn commit: r1140482 - /subversion/branches/svn-bisect/BRANCH-README

From: Arwin Arni <arwin_at_collab.net>
Date: Tue, 28 Jun 2011 15:42:42 +0530

On Tuesday 28 June 2011 03:32 PM, Stefan Sperling wrote:
> On Tue, Jun 28, 2011 at 03:12:22PM +0530, Arwin Arni wrote:
>> On Tuesday 28 June 2011 03:01 PM, Noorul Islam K M wrote:
>>>> +svn bisect start [-rN[:M]]
>>>> +
>>> When we discussed you had a concern that above syntax is different from
>>> the normal svn sub command syntax. Is this finalized?
>>>
>> I wouldn't say it's finalized.. I simply wrote down a spec as a rough draft.
>> I'm sure the community will have some ideas about this. (Like implementing
>> a sub-subcommand interface of some sort.)
> I'd say just have a set of long options that are mutually exclusive,
> one for each "subcommand".
>
> svn bisect --start
> svn bisect --good
> etc.
>
> This will be easiest to do with the current argument parsing code, and
> also means people can type things in any order they like (--good -r42,
> or -r42 --good).
>
> Note though that the option names are global. But I think the
> option names you need (start, bad, good, skip, reset, run) are
> still available.

I was hoping to achieve an interface that was most natural, and similar
to git.

But, I guess if we're stuck with the long option way of doing things,
then that's fine.

More thoughts on whether we can implement a sub-subcommand table or
something of that
sort?

Regards,
Arwin Arni
Received on 2011-06-28 12:13:25 CEST

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.