aboutsummaryrefslogtreecommitdiffstats
path: root/admin
diff options
context:
space:
mode:
Diffstat (limited to 'admin')
-rw-r--r--admin/notes/bzr13
1 files changed, 10 insertions, 3 deletions
diff --git a/admin/notes/bzr b/admin/notes/bzr
index 5600c9badb0..f4907063d0b 100644
--- a/admin/notes/bzr
+++ b/admin/notes/bzr
@@ -12,10 +12,17 @@ difficult.
12 12
13http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html 13http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html
14 14
15The exception is, if you know that the change will be difficult to
16merge to the trunk (eg because the trunk code has changed a lot).
17In that case, it's helpful if you can apply the change to both trunk
18and branch yourself (when committing the branch change, indicate
19in the commit log that it should not be merged to the trunk; see below).
20
15* Backporting a bug-fix from the trunk to a branch (e.g. "emacs-23"). 21* Backporting a bug-fix from the trunk to a branch (e.g. "emacs-23").
16Label the commit as a backport, e.g. by starting the commit message with 22Indicate in the commit log that there is no need to merge the commit
17"Backport:". This is helpful for the person merging the release branch 23to the trunk. Anything that matches `bzrmerge-skip-regexp' will do;
18to the trunk. 24eg start the commit message with "Backport:". This is helpful for the
25person merging the release branch to the trunk.
19 26
20http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00262.html 27http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00262.html
21 28