mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-27 07:37:33 +00:00
Code Issues Releases Activity

Update X-Debbugs-CC details.

Browse Source 
Remove Mail-Followup-To, since it is no longer set.
Mention replacement of addresses in new reports.
Mention bazaar --fixes.
Mention debbugs-submit administrivia setting.
Mention how to test Debbugs changes.
This commit is contained in:
Glenn Morris 2010-01-23 15:11:24 -08:00
parent 02c6d0d0f2
commit 9630d49eae
1 changed files with 38 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
admin/notes/bugtracker
View File

@ -35,6 +35,7 @@ So you need to explicitly CC him/her (and anyone else you like).
(Many people think the submitter SHOULD be automatically subscribed (Many people think the submitter SHOULD be automatically subscribed
to subsequent discussion, but this does not seem to be implemented. to subsequent discussion, but this does not seem to be implemented.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078) 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, since this may generate a Do NOT send a separate copy to the bug list, since this may generate a
new report. The only time to send mail to the bug list is to create a new report. The only time to send mail to the bug list is to create a
@ -61,18 +62,9 @@ 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. This is in the subsequent discussion will end up creating a new bug. This is
annoying. annoying.
Note that the way this feature works is perhaps not ideal (Bug#1720). If a new report contains X-Debbugs-CC in the input, this is
If X-Debbugs-CC: was specifed by a real header, that header is removed converted to a real Cc header in the output. (See Bug#1720).
in the mail sent out to the bug list, and the addresses merged into It is also merged into the Resent-CC header (see below).
the Resent-CC header (see below). They don't appear as an explicit CC:
header, nor do they appear in the Reply-To: header. So people you
X-Debbugs-CC are not included in any following discussion unless they are
manually cc'd. So this feature really only serves to notify them that
a bug has been filed. It's then up to them to follow any subsequent
discussion.
If X-Debbugs-CC were merged into the Reply-To header, this might work
more the way people expect.
** How does Debbugs send out mails? ** How does Debbugs send out mails?
@ -88,9 +80,9 @@ Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries
The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases.
A new report also has: In a new report, any "bug-gnu-emacs", "emacs-pretest-bug", or
"submit@debbugs" address in the original To or Cc is replaced by
Mail-Followup-To: bug submitter, 123@debbugs.gnu.org 123@debbugs in the mail that gets sent out to the bug list.
** To not get acknowledgement mail from the tracker, ** To not get acknowledgement mail from the tracker,
add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus,
@ -124,10 +116,10 @@ When you close a bug, you get a message matching:
^X-Emacs-PR-Message: closed ^X-Emacs-PR-Message: closed
** How to avoid multiple copies of mails. ** How to avoid multiple copies of mails.
When you reply to a bug, respect the Reply-To address, ie send mail If you reply to reports in the normal way, this should work fine.
only to the submitter address and the numbered bug address. Do not Basically, reply only to the numbered bug address (and any individual
send mail direct to bug-gnu-emacs or emacs-pretest-bug unless you are people's addresses). Do not send mail direct to bug-gnu-emacs or
reporting a new bug. emacs-pretest-bug unless you are reporting a new bug.
** To close bug #123 (for example), send mail ** To close bug #123 (for example), send mail
@ -362,7 +354,7 @@ bug number.
Similarly, when you close a bug, it can be helpful to include the Similarly, when you close a bug, it can be helpful to include the
relevant ChangeLog entry in the message to the bug tracker, so people relevant ChangeLog entry in the message to the bug tracker, so people
can see eaxctly what the fix was. can see exactly what the fix was.
*** bug-reference-mode *** bug-reference-mode
@ -373,6 +365,17 @@ the bug web-pages.
http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
** Bazaar stuff
*** You can use the commit --fixes emacs:123 to mark that a commit fixes
Emacs bug 123. You will first need to add a line to your bazaar.conf
(untested):
bugtracker_emacs_url = http://debbugs.gnu.org/{id}
Note that all this does is add some metadata to the commit, it doesn't
actually mark the bug as closed in the tracker.
** Gnus-specific voodoo ** Gnus-specific voodoo
*** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group *** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group
@ -456,3 +459,18 @@ recipient: emacs-bug-tracker AT debbugs\.gnu\.org
The latter is because that is the address that debbugs actually sends to. The latter is because that is the address that debbugs actually sends to.
An /etc/aliases entry redirects it to the real emacs-bug-tracker address. An /etc/aliases entry redirects it to the real emacs-bug-tracker address.
** Administrivia
The debbugs-submit list should have the administrivia option off,
else it can by mistake filter out requests to subscribe to bugs.
But, this feature doesn't work anyway (see bug#5439).
** How to test changes
Add an entry to /etc/debbugs/Maintainers like:
mytest my.email.address
Then if you do all your testing with 'Package: mytest', the resulting
mails should only go to your email address.