diff options
Diffstat (limited to 'admin/notes/bugtracker')
| -rw-r--r-- | admin/notes/bugtracker | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker index c39458184f6..f3bc3045542 100644 --- a/admin/notes/bugtracker +++ b/admin/notes/bugtracker @@ -8,7 +8,7 @@ This is 95% of all you will ever need to know. ** How do I report a bug? 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 (or +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? @@ -53,7 +53,7 @@ i) Your report will be assigned a number and generate an automatic reply. ii) Optionally, you can set some database parameters when you first report a bug (see "Setting bug parameters" below). -iii) If you want to CC: someone, use X-Debbugs-CC: (note this only +iii) If you want to Cc someone, use X-Debbugs-Cc: (note this only applies to _new_ reports, not followups). Once your report is filed and assigned a number, it is sent out to the @@ -64,8 +64,8 @@ quiet@debbugs.gnu.org. ** How do I reply to an existing bug report? Reply to 123@debbugs.gnu.org, replacing 123 with the number of the bug you are interested in. NB this only sends mail to the -bug-list, it does NOT send a CC to the original bug submitter. -So you need to explicitly CC him/her (and anyone else you like). +bug-list, it does NOT send a Cc to the original bug submitter. +So you need to explicitly Cc him/her (and anyone else you like). (This works the same way as all the Emacs mailing lists. We generally don't assume anyone who posts to a list is subscribed to it, so we cc everyone on replies.) @@ -95,23 +95,23 @@ normal bug reporting.) ** 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. -Instead, use "X-Debbugs-CC:". This ensures the Cc address(es) will get a +Instead, use "X-Debbugs-Cc:". This ensures the Cc address(es) will get a mail with the bug report number in. If you do not do this, each reply in the subsequent discussion might end up creating a new bug. 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.) +better to use X-Debbugs-Cc.) If you want to send copies to more than one address, add them -comma-separated in only one X-Debbugs-CC line. +comma-separated in only one X-Debbugs-Cc line. Like any X-Debbugs- header, this one can also be specified in the 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) -It is also merged into the Resent-CC header (see below). +It is also merged into the Resent-Cc header (see below). ** How does Debbugs send out mails? @@ -120,15 +120,15 @@ header is unchanged. In new reports only (at present), the To: address is altered as follows. Any "bug-gnu-emacs", "emacs-pretest-bug", or "submit@debbugs" address is replaced by 123@debbugs in the mail that gets sent out. (This also applies to any -Cc: header, though you should be using X-Debbugs-CC instead in new +Cc: header, though you should be using X-Debbugs-Cc instead in new reports). The original header is stored as X-Debbugs-Original-To, if -it was changed. Any X-Debbugs-CC is merged into the Cc. +it was changed. Any X-Debbugs-Cc is merged into the Cc. Mails arriving at the bug list have the following Resent-* headers: Resent-From: person who submitted the bug Resent-To: owner@debbugs.gnu.org -Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries +Resent-Cc: maintainer email address, plus any X-Debbugs-Cc: entries The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. @@ -239,7 +239,7 @@ The control server ignores anything after the last line above. So you can place control commands at the beginning of a reply to a bug report, and Bcc: the control server (note the commands have no effect if you just send them to the bug-report number). Bcc: is better than Cc: -in case people use Reply-to-All in response. +in case people use Reply-To-All in response. Some useful control commands: |