aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes/bugtracker
diff options
context:
space:
mode:
authorGlenn Morris2013-05-09 09:14:05 -0700
committerGlenn Morris2013-05-09 09:14:05 -0700
commitf4ca11f82870e0ab403e2f66fc3ec1989f40f317 (patch)
tree8ba1aeab0e824bef9b683b4464df29411d259848 /admin/notes/bugtracker
parent4465bfb465ffdecc9422bd2f3cd34440c7710dfa (diff)
downloademacs-f4ca11f82870e0ab403e2f66fc3ec1989f40f317.tar.gz
emacs-f4ca11f82870e0ab403e2f66fc3ec1989f40f317.zip
X-Debbugs-CC clarifications
Diffstat (limited to 'admin/notes/bugtracker')
-rw-r--r--admin/notes/bugtracker24
1 files changed, 14 insertions, 10 deletions
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index 9957bc9b567..7947b17973b 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -8,7 +8,8 @@ This is 95% of all you will ever need to know.
8 8
9** How do I report a bug? 9** How do I report a bug?
10Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org. 10Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org.
11If you want to Cc someone, use an "X-Debbugs-CC" header instead. 11If you want to Cc someone, use an "X-Debbugs-CC" header (or
12pseudo-header, see below) instead.
12 13
13** How do I comment on a bug? 14** How do I comment on a bug?
14Reply to a mail on the bug-gnu-emacs list in the normal way. 15Reply to a mail on the bug-gnu-emacs list in the normal way.
@@ -52,8 +53,8 @@ i) Your report will be assigned a number and generate an automatic reply.
52ii) Optionally, you can set some database parameters when you first 53ii) Optionally, you can set some database parameters when you first
53report a bug (see "Setting bug parameters" below). 54report a bug (see "Setting bug parameters" below).
54 55
55iii) If you want to CC: someone, use X-Debbugs-CC: (this is important; 56iii) If you want to CC: someone, use X-Debbugs-CC: (note this only
56see below). 57applies to _new_ reports, not followups).
57 58
58Once your report is filed and assigned a number, it is sent out to the 59Once your report is filed and assigned a number, it is sent out to the
59bug mailing list. In some cases, it may be appropriate to just file a 60bug mailing list. In some cases, it may be appropriate to just file a
@@ -92,15 +93,18 @@ but create duplicates and errors. (It is possible, but unlikely, that
92you might want to have a dialog with the owner address, outside of 93you might want to have a dialog with the owner address, outside of
93normal bug reporting.) 94normal bug reporting.)
94 95
95** When reporting a bug, to send a Cc to another address 96** When reporting a new bug, to send a Cc to another address
96(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. 97(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
97Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a 98Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a
98mail with the bug report number in. If you do not do this, each reply 99mail with the bug report number in. If you do not do this, each reply
99in the subsequent discussion will end up creating a new bug. 100in the subsequent discussion might end up creating a new bug.
100This is annoying. 101This is annoying. (So annoying that a form of message-id tracking has
102been implemented to hopefully stop this happening, but it is still
103better to use X-Debbugs-CC.)
101 104
102(So annoying that a form of message-id tracking has been implemented 105Like any X-Debbugs- header, this one can also be specified in the
103to hopefully stop this happening, but it is still better to use X-Debbugs-CC.) 106pseudo-header (see below), if your mail client does not let you add
107"X-" headers.
104 108
105If a new report contains X-Debbugs-CC in the input, this is 109If a new report contains X-Debbugs-CC in the input, this is
106converted to a real Cc header in the output. (See Bug#1780,5384) 110converted to a real Cc header in the output. (See Bug#1780,5384)
@@ -218,8 +222,8 @@ Package: emacs
218Version: 23.0.60 222Version: 23.0.60
219Severity: minor 223Severity: minor
220 224
221This can also include tags. Some things (e.g. submitter) don't seem to 225This can also include tags, or any X-Debbugs- setting.
222work here. 226Some things (e.g. submitter) don't seem to work here.
223 227
224Otherwise, send mail to the control server, control@debbugs.gnu.org. 228Otherwise, send mail to the control server, control@debbugs.gnu.org.
225At the start of the message body, supply the desired commands, one per 229At the start of the message body, supply the desired commands, one per