summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--HACKING2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index a603b6953..8e7764baf 100644
--- a/HACKING
+++ b/HACKING
@@ -178,7 +178,7 @@
over-arching change, you should use a dedicated topic branch, and
only merge that back once it is reasonably stable.
-* The 'next' branch should be kept regularly merged into the 'master'
+* The 'master' branch should be kept regularly merged into the 'next'
branch. It is advisable to merge only after a set of related
commits have been applied, to avoid introducing too much noise in
the history.