'bzr branch' behaving differently when using a shared repository

[Jelmer Vernooij]

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.

[Erik Bågfors (zindar)]

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
>

[Aaron Bentley (abentley)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jelmer Vernooij wrote:
> 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.

I think this sort of thing is better discussed on the list than through
the bug tracker.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEvvbg0F+nu1YWqI0RAmnLAKCBZKenWPT4apgPS7qq8IY3ciY8tQCdFXFD
oU+UMd3Z0CehEIdH7pEGZmo=
=fQ1o
-----END PGP SIGNATURE-----

[Martin Pool (mbp)]

Confirmed

[Martin Pool (mbp)]

We had some discussion of this on irc; abentley mbp and lifeless agree it would be ok to change the default. It should be enough to just change cmd_init_repo to use a different initial default.

This won't fix existing repositories though because the value used when they were created is remembered.

[Vincent Ladeuil (vila)]

Fixed in attached patch

[Jelmer Vernooij (jelmer)]

Patch appears to be missing?h

[Vincent Ladeuil (vila)]

Doh !

Here it is.

[Vincent Ladeuil (vila)]

Larstiq provided a better patch that has been merged.