Mercurial > emacs

comparison admin/notes/bugtracker @ 101597:fb07b238e55a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update message-dont-reply-to-names section. Mention the wonderful spam filter.
author Glenn Morris <rgm@gnu.org>
date Wed, 28 Jan 2009 02:54:46 +0000
parents 80672b7f9b76
children 9268e7d84955
comparison
equal deleted inserted replaced
101596:386ff0ad2b5d 101597:fb07b238e55a
35 35
36 Do NOT send a separate copy to the bug list, since this may generate a 36 Do NOT send a separate copy to the bug list, since this may generate a
37 new report. The only time to send mail to the bug list is to create a 37 new report. The only time to send mail to the bug list is to create a
38 new report. 38 new report.
39 39
40 Gnus users can add "\\(\\(emacs-pretest-bug\\|bug-gnu-emacs\\)@gnu\\.org\\|\ 40 Gnus users can add the following to message-dont-reply-to-names;
41 \\(submit\\|control\\)@emacsbugs\\.donarmstrong\\.com\\)" 41 similarly with Rmail and rmail-dont-reply-to-names:
42 to message-dont-reply-to-names. 42
43 43 "\\(emacs-pretest-bug\\|bug-gnu-emacs\\)@gnu\\.org\\|\
44 Similarly, RMAIL users can use rmail-dont-reply-to-names. They might 44 \\(\\(submit\\|control\\|owner\\)@emacsbugs\\.\\|bug-submit-list@\\)\
45 also need to ignore "bug-submit-list@donarmstrong.com" since it 45 donarmstrong\\.com"
46 appears in the "Resent-To" header of reports, and for a long time 46
47 RMAIL erroneously included this address in replies. Likewise for 47 The "bug-submit-list@donarmstrong.com" and
48 "owner@emacsbugs.donarmstrong.com", which can appear in the 48 "owner@emacsbugs.donarmstrong.com" entries are there because they can
49 "Resent-CC:" header (but it is possible, outside of normal bug 49 appear in the "Resent-To" and "Resent-CC" headers, respectively. For a
50 reporting, that you might want to have a dialog with this address). 50 long time Rmail erroneously included these headers in replies. If you
51 correspond with an Rmail user on a bug, these addresses may end up in
52 the Cc. Mailing to them does nothing but create duplicates and errors.
53 (It is possible you might want to have a dialog with the owner
54 address, outside of normal bug reporting.)
51 55
52 ** When reporting a bug, to send a Cc to another address 56 ** When reporting a bug, to send a Cc to another address
53 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. 57 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
54 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a 58 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a
55 mail with the bug report number in. If you do not do this, each reply 59 mail with the bug report number in. If you do not do this, each reply
226 230
227 The above page is accessible from the "Options" section at the end of 231 The above page is accessible from the "Options" section at the end of
228 the "main list of bugs" page. Select bugs "in package" = emacs; 232 the "main list of bugs" page. Select bugs "in package" = emacs;
229 "newest bugs" = 100. (I have no idea how you get to that Options 233 "newest bugs" = 100. (I have no idea how you get to that Options
230 section without having to go through the bug list page first...) 234 section without having to go through the bug list page first...)
235
236 ** Mails to the bug tracker disappear
237
238 Apparently it has some kind of spam filter that sometimes silently
239 discards valid mails. Adding a subject (pointless in control messages)
240 may help.