[Bulk] Re: [rfc] bzr-colo into core

Jelmer Vernooij jelmer at canonical.com
Wed Mar 23 13:49:58 UTC 2011


On Wed, 2011-03-23 at 09:29 -0400, Gordon Tyler wrote:
> On 3/23/2011 8:53 AM, Jelmer Vernooij wrote:
> > On Wed, 2011-03-23 at 08:44 -0400, Gordon Tyler wrote:
> >> On 3/22/2011 10:18 PM, Martin Pool wrote:
> >>>  * I feel the user model is in an unhappy valley where users do need
> >>> to know about the repository, branch, wt components, but the ui and
> >>> documentation don't really expose them as such; instead we tend to
> >>> talk about the stylized arrangements such as lightweight checkouts and
> >>> standalone branches.
> >>>
> >>>  * The thing that is closest to being a default, standalone branches,
> >>> is not something we would normally recommend at all.
> >>
> >> So how about this: `bzr branch URL [DIR]` will create a colo repo if
> >> there is no shared repo in a parent dir. If URL contains a colo repo,
> >> all branches would be cloned. A `--standalone` option can be added to
> >> make it work like it currently does.
> >>
> >> The problem with the bzr-colo implementation is that the URL to a
> >> particular branch is a little messy if you want to fetch only one
> >> branch. The only way I can see that getting resolved is by adding some
> >> kind of indicator to the URL for which branch to fetch. Whether that
> >> gets resolved to the .bzr/branches/BRANCH or if branches are
> >> incorporated into repo metadata, I don't know.
> > I think it would be confusing for "bzr branch" to create more than one
> > branch. Perhaps this is a good opportunity to remove the "clone" alias
> > from "bzr branch" and turn it into its own command? "bzr clone" could
> > create a full clone of the remote control dir, including all of the
> > branches present.
> Good point. That would change `bzr branch` to be solely for creating
> branching in an existing local repo? `bzr clone` would be the command
> for fetching remote repos or standalone branches.
It would still be used for cloning individual branches rather than
collections of branches (for which clone would be used), so it would
stay consistent with the current bzr behaviour. 

Cheers,

Jelmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110323/a7e3cee3/attachment.pgp>


More information about the bazaar mailing list