diff options
| author | Glenn Morris <rgm@gnu.org> | 2011-05-14 12:11:47 -0700 |
|---|---|---|
| committer | Glenn Morris <rgm@gnu.org> | 2011-05-14 12:11:47 -0700 |
| commit | 1adfa36f8373768c62d76e018dcbfe039bc6ad9f (patch) | |
| tree | 5424dcdba33bb697ebbe107eb9d69bff33fc6652 /admin/notes/bugtracker | |
| parent | dc5e0b5aace520e202bbbcdf0e728a4bdc72e043 (diff) | |
| download | emacs-1adfa36f8373768c62d76e018dcbfe039bc6ad9f.tar.gz | |
* admin/notes/bugtracker: Small updates.
Diffstat (limited to 'admin/notes/bugtracker')
| -rw-r--r-- | admin/notes/bugtracker | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker index f2805eae443..04721e4cec3 100644 --- a/admin/notes/bugtracker +++ b/admin/notes/bugtracker @@ -63,13 +63,16 @@ 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. +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.) (Many people think the submitter SHOULD be automatically subscribed to subsequent discussion, but this does not seem to be implemented. -See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078) -See also http://debbugs.gnu.org/5439 +See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078 +See also http://debbugs.gnu.org/5439 ) Do NOT send a separate copy to the bug list address, since this may generate a new report. The only time to send mail to the bug list @@ -85,9 +88,9 @@ The "owner@debbugs.gnu.org" entry is there because it appears in the "Resent-To" header. For a long time Rmail erroneously included such headers in replies. If you correspond with an Rmail user on a bug, these addresses may end up in the Cc. Mailing to them does nothing -but create duplicates and errors. (It is possible you might want to -have a dialog with the owner address, outside of normal bug -reporting.) +but create duplicates and errors. (It is possible, but unlikely, that +you might want to have a dialog with the owner address, outside of +normal bug reporting.) ** When reporting a bug, to send a Cc to another address (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. |