08:16 < abentley> Better phrasing: 'what circumstances should cause us to produce a working tree in a repository branch'?

[Aaron Bentley]

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

Denys Duchier wrote:
> Robert Collins <robertc at robertcollins.net> writes:
> 
> 
>>This interesting question just came up.
>>
>>We're still chatting on IRC, but I thought list input would be good.
>>
>>Current things being discussed:
>> * flag in the repository [defaults to do not create]e
> 
> 
> -1.  I am against such a flag.

Could you expand on why?  I can imagine some users would always want
working trees, and others would never want working trees, at least on a
per-repository basis.

>> * command line option [orthogonal to such a flag?]
>> * different command to represent the different intent.
> 
> 
> How about something along those lines:
> 
> bzr create [--repository] [--branch | --clone BRANCH] [--checkout] [LOCATION]

Personally, I think this would make things harder for everyone.  Point
taken, bzr branch is really a bunch of different operations.  But I
think only a few combinations are useful, and we can break those out as
separate commands.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD6myB0F+nu1YWqI0RAvgpAJ4nm+RITAF53m+U5rZ+NOlPghYS3QCePt6o
VCPTzvd7CuAgmsxv1rFywZ8=
=DhpC
-----END PGP SIGNATURE-----