36 === Creating a (named) branch ===

    36 === Using (named) branches ===

    37 We prefer not to use (named) branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.

    37 Branches are alternative commit histories. Changes done in one branch can be merged into other branches as needed.

    38 So for small code contributions, use unnamed branches instead (see below).

    38 Most main development happens on the main repository branch "default".

    39 However, if you are going to write code that is more a project than a patch and that will take dozens of commits, feel free to use a (named) branch.

    39 

    40 We prefer not to use separate branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.

    41 So for small code contributions, use "unnamed branches" instead (see below).

    42 

    43 However, if you are going to write code that is more a project than a patch and that will take dozens of commits, feel free to do that work on a new branch.