# HG changeset patch
# User sheepluva
# Date 1452803420 0
# Node ID 76c078df2785df78e836b4cc088c5f65fb63dc3c
# Parent  03def791ae0bf0d1ab6f9d47b12db9bd8bc9df54
Edited via web interface

diff -r 03def791ae0b -r 76c078df2785 ContributingCode.wiki
--- a/ContributingCode.wiki	Thu Jan 14 20:26:42 2016 +0000
+++ b/ContributingCode.wiki	Thu Jan 14 20:30:20 2016 +0000
@@ -33,10 +33,14 @@
 
 TODO
 
-=== Creating a (named) branch ===
-We prefer not to use (named) branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.
-So for small code contributions, use unnamed branches instead (see below).
-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.
+=== Using (named) branches ===
+Branches are alternative commit histories. Changes done in one branch can be merged into other branches as needed.
+Most main development happens on the main repository branch "default".
+
+We prefer not to use separate branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.
+So for small code contributions, use "unnamed branches" instead (see below).
+
+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.
 
 To create a new branch use {{{hg branch}}} followed by the name of the new branch, before committing the first code.