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

[Jari Aalto]

Aaron Bentley <aaron.bentley at utoronto.ca> writes:
>
>>>>bzr create [--repository] [--branch | --clone BRANCH] [--checkout] [LOCATION]
> 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"
>
>
>> 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 tha
I concur that the command should be logical first and then there can
be "shortcuts". We must remember that bzr is not all command line, but
there will be 3rd party software that integrate to these commands
(Like Emacs ot orher graphcal GUI etc.). The notation suggested above:

      bzr create ...

is the most logical. It is clear and the documentation is in one place

   bzr help create

The --checkout  relevant in this context, so it makes sense to have it
here as well. 

There are several solutions that can be to ease the command line typing:

      1) user creates aliases, or shell scripts
      2) there are "shotcuts" like in "bzr st".

Firts of all the programs shou *not* be designed form command line
point of view, but from the consistent UI point of view, whether that
requires --long-names.

Jari