Re: Naming scheme for branches which will not be merged.

[Stefan Monnier]

> What naming scheme should we use? Either prefix the branch name with
> something really obvious, like “dont-merge/BRANCH-NAME”, so that
> people who unaware of this convention don't make that mistake. Or
> prefix it with any of the usual words that denote in-development, such
> as “dev/BRANCH-NAME”.

I vote against `dont-merge', and propose `scratch' as another contender.

> Should the creator of the branch add his/her username to it? i.e.
> “dont-merge/malabarba/BRANCH-NAME”.

I don't see a strong need to put the user in the branch name, unless you
want to state explicitly that other developers shouldn't mess with it.


        Stefan