diff options
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/notes/bzr | 13 |
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 | ||
| 13 | http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html | 13 | http://lists.gnu.org/archive/html/emacs-devel/2010-03/msg01124.html |
| 14 | 14 | ||
| 15 | The exception is, if you know that the change will be difficult to | ||
| 16 | merge to the trunk (eg because the trunk code has changed a lot). | ||
| 17 | In that case, it's helpful if you can apply the change to both trunk | ||
| 18 | and branch yourself (when committing the branch change, indicate | ||
| 19 | in 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"). |
| 16 | Label the commit as a backport, e.g. by starting the commit message with | 22 | Indicate 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 | 23 | to the trunk. Anything that matches `bzrmerge-skip-regexp' will do; |
| 18 | to the trunk. | 24 | eg start the commit message with "Backport:". This is helpful for the |
| 25 | person merging the release branch to the trunk. | ||
| 19 | 26 | ||
| 20 | http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00262.html | 27 | http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00262.html |
| 21 | 28 | ||