Commit f4ca11f8 authored by Glenn Morris's avatar Glenn Morris

X-Debbugs-CC clarifications

parent 4465bfb4
...@@ -8,7 +8,8 @@ This is 95% of all you will ever need to know. ...@@ -8,7 +8,8 @@ This is 95% of all you will ever need to know.
** How do I report a bug? ** How do I report a bug?
Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org. Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org.
If you want to Cc someone, use an "X-Debbugs-CC" header instead. If you want to Cc someone, use an "X-Debbugs-CC" header (or
pseudo-header, see below) instead.
** How do I comment on a bug? ** How do I comment on a bug?
Reply to a mail on the bug-gnu-emacs list in the normal way. Reply 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. ...@@ -52,8 +53,8 @@ i) Your report will be assigned a number and generate an automatic reply.
ii) Optionally, you can set some database parameters when you first ii) Optionally, you can set some database parameters when you first
report a bug (see "Setting bug parameters" below). report a bug (see "Setting bug parameters" below).
iii) If you want to CC: someone, use X-Debbugs-CC: (this is important; iii) If you want to CC: someone, use X-Debbugs-CC: (note this only
see below). applies to _new_ reports, not followups).
Once your report is filed and assigned a number, it is sent out to the Once your report is filed and assigned a number, it is sent out to the
bug mailing list. In some cases, it may be appropriate to just file a bug 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 ...@@ -92,15 +93,18 @@ but create duplicates and errors. (It is possible, but unlikely, that
you might want to have a dialog with the owner address, outside of you might want to have a dialog with the owner address, outside of
normal bug reporting.) normal bug reporting.)
** When reporting a bug, to send a Cc to another address ** When reporting a new bug, to send a Cc to another address
(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. (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 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 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. in the subsequent discussion might end up creating a new bug.
This is annoying. This is annoying. (So annoying that a form of message-id tracking has
been implemented to hopefully stop this happening, but it is still
better to use X-Debbugs-CC.)
(So annoying that a form of message-id tracking has been implemented Like any X-Debbugs- header, this one can also be specified in the
to hopefully stop this happening, but it is still better to use X-Debbugs-CC.) pseudo-header (see below), if your mail client does not let you add
"X-" headers.
If a new report contains X-Debbugs-CC in the input, this is If a new report contains X-Debbugs-CC in the input, this is
converted to a real Cc header in the output. (See Bug#1780,5384) converted to a real Cc header in the output. (See Bug#1780,5384)
...@@ -218,8 +222,8 @@ Package: emacs ...@@ -218,8 +222,8 @@ Package: emacs
Version: 23.0.60 Version: 23.0.60
Severity: minor Severity: minor
This can also include tags. Some things (e.g. submitter) don't seem to This can also include tags, or any X-Debbugs- setting.
work here. Some things (e.g. submitter) don't seem to work here.
Otherwise, send mail to the control server, control@debbugs.gnu.org. Otherwise, send mail to the control server, control@debbugs.gnu.org.
At the start of the message body, supply the desired commands, one per At the start of the message body, supply the desired commands, one per
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment