creating checkouts, bound branches and standalone branches from an existing branch

[Jari Aalto]

jblack at merconline.com (James Blackwell) writes:

> On Sat, Feb 11, 2006 at 11:42:41PM +0100, Denys Duchier wrote:
>
>> I would propose that:
>> 
>> 	bzr get --commit=remote       URL PATH
>>      bzr get --commit=local,remote URL PATH
>>      bzr get --commit=local        URL PATH
>
> I propose the following:
> ------------------------
>  bzr branch                   |  Defaults to branch --lightly-bound.
>                               |
>  bzr branch [-c|--checkout]   |  A checkout.
>                               |
>  bzr branch [-u|--unbound]    |  unbound branch (with or w/o repo)
>                               |
>  bzr branch [-b|--bound]      |  a fully bound branch. No remote access,
>                               |  no commit. Probably a bit rare
>                               |
>  bzr branch --lightly-bound   |  a lightly bound branch that breaks 
>                               |  binding on
>                               |  commit if the remote branch is
>                               |  uncommittable*

Hm, does the options have be in form "spoken englist" like syntax? I
would rather call this one:

       bzr branch --bound-light

... where the master word is mentioned first: "--bound". This would
also help tools that offer completion support for commands (bash,
Emacs etc.)

In linux they use term "bind" and mount(1) uses option "--bind". What
you do think about that term compared to "bound"?


>  * I can't decide whether this should be a lightly bound branch. One idea 
>    that appeals to me is the idea of a branch that decides whether its
>    bound or not based upon the results of the first commit. If the first
>    commit succeeds, then its fully bound. If the first commit fails, then
>    its unbound.
>
>
> With the following aliases: 
> ---------------------------
>  checkout & co                | alias for "branch --checkout"
>  get, clone                   | alias for branch
>
>
> With consideration given to:
> --------------------------------
>  bzr rebranch [same options as | Converts a branch from one type to
>                above]          | another, provided the result is possible
>                                  and sane.

Wouldn't this be a branch command? I'd see it belonging to:

         branch --action=convert <rest of the options>

Or simply

         branch --convert <rest of the options>

Jari