On 2008-03-17 13:14:07 +0100, David Kågedal wrote:

quoted text
> so, the usage string is wrong. In fact, the described usage string
> is only for the default action to create a new branch.

Yes, this is far from pretty.

quoted text
> Maybe it would have been better to have separate stg subcommands?
>
>   stg branch NAME [COMMIT]
>   stg list-branches
>   stg rename-branch OLD NEW
>   ... etc ...

My first thought was another level of subcommands:

  stg branch NAME [COMMIT]
  stg branch list
  stg branch rename OLD NEW

But this would create ambiguities -- how do I create a branch called
"list"?. One could go with something like

  stg branch NAME [COMMIT]
  stg branch/list
  stg branch/rename OLD NEW

but this is highly non-standard, and would probably confuse every
single new user. Perhaps with dashes instead:

  stg branch NAME [COMMIT]
  stg branch-list
  stg branch-rename OLD NEW

Which is essentially what you proposed, but with more regular (and
more tab-completion-friendly) names.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html