Mercurial > emacs

comparison admin/notes/bugtracker @ 108915:f82a793ed06b

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
* admin/notes/bugtracker: Note on some emacs-bug-tracker minutiae.
author Glenn Morris <rgm@gnu.org>
date Tue, 08 Jun 2010 23:53:17 -0700
parents 85d6810f63ed
children 0d62b248cade
comparison
equal deleted inserted replaced
108914:e7f12b4b8ef7 108915:f82a793ed06b
147 ** Not interested in tracker control messages (tags being set, etc)? 147 ** Not interested in tracker control messages (tags being set, etc)?
148 Discard mails matching: 148 Discard mails matching:
149 149
150 ^X-GNU-PR-Message: (transcript|closed) 150 ^X-GNU-PR-Message: (transcript|closed)
151 151
152 ** Not receiving messages in response to your control commands?
153 The messages debbugs sends out in response to control-server commands
154 always have headers To: your@email, and Cc: tracker@debbugs.gnu.org
155 (the latter is an alias for the emacs-bug-tracker mailing list).
156 These are also the addresses to which a copy of the response is sent.
157 (In general, there need not be any relation between the To: and Cc:
158 headers visible in a message and where debbugs actually sends it.)
159 If you used an X-Debbugs-No-Ack header, however, a copy is _not_ sent
160 to you, but the To: header is unchanged. If you are subscribed to the
161 emacs-bug-tracker mailing list and have duplicate suppression turned
162 on, the presence of your address in the To: header will cause Mailman
163 to not send you a list copy, because it thinks you have received a
164 direct copy. If you used X-Debbugs-No-Ack, this is not the case, and
165 you won't get any copy at all. If this bothers you, don't use both
166 X-Debbugs-No-Ack and Mailman duplicate suppression for the
167 emacs-bug-tracker mailing list, just pick one or the other.
168
152 ** How to avoid multiple copies of mails. 169 ** How to avoid multiple copies of mails.
153 If you reply to reports in the normal way, this should work fine. 170 If you reply to reports in the normal way, this should work fine.
154 Basically, reply only to the numbered bug address (and any individual 171 Basically, reply only to the numbered bug address (and any individual
155 people's addresses). Do not send mail direct to bug-gnu-emacs or 172 people's addresses). Do not send mail direct to bug-gnu-emacs or
156 emacs-pretest-bug unless you are reporting a new bug. 173 emacs-pretest-bug unless you are reporting a new bug.