[PATCH 1 of 4] commit: try to clarify when to use --new-branch

[timeless]

Matt Mackall wrote:
> On Mon, 2015-12-07 at 14:23 -0600, timeless wrote:
>> commit: try to clarify when to use --new-branch
>
> --new-branch is a flag on push, so this is very confusing

oops, I meant --close-branch :)

>> +      If you are thinking about closing a branch, but you never shared
>> +      it, you should consider making it secret (see :hg:`help phase`) or
>> +      obsolete (see :hg:`help obsolete`), or stripping it
>> +      (see :hg:`help strip`) instead of merely closing it.
>
> The first piece of advice is ok, I guess. But if you don't understand
> named branches.. dumping phases onto the pile is probably asking a lot
> of a user. I might suggest a simpler, less assertive "see also:
> phases".

I sent a revised version.

> The second can't be used without an experimental out-of-tree
> extensions. Definitely not advice we want in core help.

At some point I need to look into help-hooks...

> The third piece refers to a destructive extension. Also probably not good advice for core commands.