creating checkouts, bound branches and standalone branches from an existing branch
Jari Aalto
jari.aalto at cante.net
Sun Feb 12 14:28:09 GMT 2006
Denys Duchier <duchier at ps.uni-sb.de> writes:
>
> [in the following, I am deliberately using the command "get" rather
> than "branch" or "checkout" to avoid confusion with
> existing/proposed concepts and/or commands.]
>
> bzr get URL PATH
>
> produce a working tree (checkout) that is lightly bound to the branch at URL.
> This is exactly the centralized model. It is unsurprising.
>
> bzr get --mirror URL PATH
> bzr get --copy URL PATH
>
> where --mirror would produce a bound branch, while --copy would
> produce a standalone branch. I just made up these options and
> probably better ones could be proposed.
>
> The point is that the primary effect of "bzr get" is to obtain a
> working tree of the project at URL. The option determines in
> particular what happens when the user commits. This could also be
> done as follows:
>
> bzr get --commit=remote URL PATH
> bzr get --commit=local,remote URL PATH
> bzr get --commit=local URL PATH
All good ideas, but I would not agree with changing the customary
convention that exiting users in other VCS's use. The term
"checkout" or "co" is carved into everyone's mind. It is not good to
create different "get" command.
Howabout
bzr {co | checkout} --type={branch | ... } [--action={mirror|copy|...}
Jari
More information about the bazaar
mailing list