[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/trunk r99391: Add a quick-start guide.

From: Glenn Morris
Subject: [Emacs-diffs] /srv/bzr/emacs/trunk r99391: Add a quick-start guide.
Date: Tue, 26 Jan 2010 20:12:26 -0800
User-agent: Bazaar (2.0.2)

revno: 99391
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Tue 2010-01-26 20:12:26 -0800
  Add a quick-start guide.
  Add details of what happens when a bug is closed.
=== modified file 'admin/notes/bugtracker'
--- a/admin/notes/bugtracker    2010-01-24 20:28:50 +0000
+++ b/admin/notes/bugtracker    2010-01-27 04:12:26 +0000
@@ -2,6 +2,36 @@
 The Emacs Bug Tracker can be found at http://debbugs.gnu.org/
+* Quick-start guide
+This is 95% of all you will ever need.
+** How do I report a bug?
+Use M-x report-emacs-bug, or send mail to address@hidden
+If you want to Cc someone, use an "X-Debbugs-CC" header instead.
+** How do I comment on a bug?
+Reply to a mail on the bug-gnu-emacs list in the normal way.
+Or send a mail to address@hidden
+If the bug is old and closed, you may have to unarchive it first.
+Send a mail to address@hidden with
+unarchive 123
+on the first line of the body.
+** How do I close a bug?
+Send a mail to address@hidden  In the body, explain
+why the bug is being closed.
+** How do I set bug meta-data?
+By mailing commands to address@hidden  Place commands at the
+start of the message body, one per line.
+severity 123 serious|important|normal|minor|wishlist
+tags 123 moreinfo|unreproducible|wontfix|patch
+* More detailed information
 For a list of all bugs, see http://debbugs.gnu.org/db/pa/lemacs.html
 This is a static page, updated once a day.  There is also a dynamic
 list, generated on request, but since there are many bug reports this
@@ -110,11 +140,7 @@
 ** Not interested in tracker control messages (tags being set, etc)?
 Discard mails matching:
-^X-Emacs-PR-Message: transcript
-When you close a bug, you get a message matching:
-^X-Emacs-PR-Message: closed
+^X-Emacs-PR-Message: (transcript|closed)
 ** How to avoid multiple copies of mails.
 If you reply to reports in the normal way, this should work fine.
@@ -131,6 +157,31 @@
 submitter; they get copies anyway so this will just result in more
 duplicate mail.
+** Details of closing a bug.
+(For information only)
+Sending a mail to 123-done does the following:
+1) Mark the bug as closed in the database.
+2) Send a mail to the original submitter telling them that their bug
+has been closed.  This mail has a header:
+X-Emacs-PR-Message: they-closed 123
+3) Send a mail to you and to the emacs-bug-tracker list confirming
+that the bug has been closed.  This mail has a header:
+X-Emacs-PR-Message: closed 123
+4) Send a copy of your mail to the bug-gnu-emacs list in exactly the
+same way as if you had sent mail to "123" (sans -done). This mail has
+X-Emacs-PR-Message: cc-closed 123
+Mail-Followup-To: address@hidden, ...
+(This is Emacs-specific.  Normally the bug list gets the same mail as in 3).
 ** Setting bug parameters.
 There are two ways to set the parameters of bugs in the database
 (tags, severity level, etc).  When you report a new bug, you can

reply via email to

[Prev in Thread] Current Thread [Next in Thread]