subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noorul Islam K M <noo...@collab.net>
Subject Re: svn commit: r1140482 - /subversion/branches/svn-bisect/BRANCH-README
Date Tue, 28 Jun 2011 09:31:56 GMT
arwin@apache.org writes:

> Author: arwin
> Date: Tue Jun 28 08:43:40 2011
> New Revision: 1140482
>
> URL: http://svn.apache.org/viewvc?rev=1140482&view=rev
> Log:
> Added a branch readme.
> * BRANCH-README : New file.
>
> Added:
>     subversion/branches/svn-bisect/BRANCH-README
>
> Added: subversion/branches/svn-bisect/BRANCH-README
> URL: http://svn.apache.org/viewvc/subversion/branches/svn-bisect/BRANCH-README?rev=1140482&view=auto
> ==============================================================================
> --- subversion/branches/svn-bisect/BRANCH-README (added)
> +++ subversion/branches/svn-bisect/BRANCH-README Tue Jun 28 08:43:40 2011
> @@ -0,0 +1,70 @@
> +This branch exists for the implementation of the svn bisect command.
> +It is maintained as a reintegrate-able branch with regular catch-up
> +merges from trunk.
> +
> +PURPOSE
> +=======
> +
> +For years, subversion users have used third-party scripts to do what
> +should rightfully be a part of subversion itself. This branch aims
> +to implement bisect functionality and make it available via the
> +public API.
> +
> +
> +SPEC
> +====
> +
> +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?

> +Initialize the bisection state.
> +If a state already exists, clean it up and create a fresh one.
> +If a revision range is specified, limit bisection to this range.
> +If a single revision is specified, bisect from that revision to HEAD.
> +If no revision is specified, bisect from revision 1 to HEAD.

Does this mean that N will be set a bad and M will be good revision
initially?

Thanks and Regards
Noorul

Mime
View raw message