'bzr branch' behaving differently when using a shared repository
Bug #53483 reported by
Jelmer Vernooij
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Vincent Ladeuil |
Bug Description
Creating a repository using 'bzr init-repo' and then creating a branch using that shared repository will result in a branch without a checkout. This is confusing, especially to people who are new to Bazaar.
Repositories are often used (and advertised) as a simple way to share history between branches for performance reasons, and as such it can be confusing that 'bzr branch' with a shared repository behaves differently.
I understand the original reason for making the no working trees the default for shared repositories, but I think that decision should be reconsidered given the way people use repositories.
Changed in bzr: | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
I'm definitely +1 on having --trees be the default.
Here it would be really good to have a better opt-parser so we can do an
alias to have --no-trees be default for ppl who want it...
/Erik
ons 2006-07-19 klockan 22:08 +0000 skrev Jelmer Vernooij:
> Public bug reported:
>
> Creating a repository using 'bzr init-repo' and then creating a branch
> using that shared repository will result in a branch without a checkout.
> This is confusing, especially to people who are new to Bazaar.
>
> Repositories are often used (and advertised) as a simple way to share
> history between branches for performance reasons, and as such it can be
> confusing that 'bzr branch' with a shared repository behaves
> differently.
>
> I understand the original reason for making the no working trees the
> default for shared repositories, but I think that decision should be
> reconsidered given the way people use repositories.
>
> ** Affects: bzr (upstream)
> Importance: Untriaged
> Status: Unconfirmed
>