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:
> Aaron Bentley <aaron.bentley at utoronto.ca> writes:
>>Could you expand on why?
> 
> 
> It's an invisible knob changing user-level command semantics.

Not necessarily invisible, and they deliberately set it.

>>>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.
> 
> 
> I don't see why you believe that separate commands are easier than separate
> options.

It's harder to type.  The help is harder to read.  It means one command
can do radically different things, including pointless things like "bzr
create --repository --checkout"

> They might be easier for the implementer, but we are discussing UI
> here.  

I think it would be harder for the implementer, but better for the UI.

> I think it is easier for a user to remember that there is one command to
> create things, and that makes it also easier to lookup the copious --help that
> should be associated with it.

People don't like copious help.  They like direct, to-the-point help.

So when you're trying to create a branch, it's harmful if the help
message includes information about creating repositories or working trees.

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

iD8DBQFD6nmc0F+nu1YWqI0RAvVgAJ9gwXuTItv1ML/tC957FHwyCGYQhgCeMyBU
j0eIfWTxh8/mFwW3erIxFLo=
=oRi0
-----END PGP SIGNATURE-----