From 741701037aa9ac7f2c79afc76003968f78050967 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Sat, 23 Jan 2010 15:25:25 -0800 Subject: [PATCH] Small fixes. --- admin/notes/bugtracker | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker index 37347903cea..30e6e86f8f9 100644 --- a/admin/notes/bugtracker +++ b/admin/notes/bugtracker @@ -59,8 +59,8 @@ reporting.) (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a mail with the bug report number in. If you do not do this, each reply -in the subsequent discussion will end up creating a new bug. This is -annoying. +in the subsequent discussion will end up creating a new bug. +This is annoying. If a new report contains X-Debbugs-CC in the input, this is converted to a real Cc header in the output. (See Bug#1720). @@ -188,8 +188,7 @@ tag:tag # all bugs with given tag See "Usertags" are very similar to tags: a set of labels that can be added -to a bug. There are two differences between normal tags and user -tags: +to a bug. There are two differences between normal tags and user tags: 1) Anyone can define any valid usertag they like. In contrast, only a limited, predefined set of normal tags are available (see above). @@ -368,7 +367,7 @@ http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html ** Bazaar stuff -*** You can use the commit --fixes emacs:123 to mark that a commit fixes +*** You can use `bzr commit --fixes emacs:123' to mark that a commit fixes Emacs bug 123. You will first need to add a line to your bazaar.conf (untested): -- 2.39.5