Mercurial > emacs
changeset 106969:5824bdf04287
Small fixes.
| author | Glenn Morris <rgm@gnu.org> |
|---|---|
| date | Sat, 23 Jan 2010 15:25:25 -0800 |
| parents | 8c9b1893adfe |
| children | f611f11aaf1f |
| files | admin/notes/bugtracker |
| diffstat | 1 files changed, 4 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/admin/notes/bugtracker Sat Jan 23 15:18:58 2010 -0800 +++ b/admin/notes/bugtracker Sat Jan 23 15:25:25 2010 -0800 @@ -59,8 +59,8 @@ (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 @@ See <http://wiki.debian.org/bugs.debian.org/usertags> "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 @@ ** 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):