Mercurial > emacs
view admin/notes/bugtracker @ 96468:5c93e68f7620
*** empty log message ***
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Tue, 01 Jul 2008 06:56:26 +0000 |
parents | 2f224124246c |
children | 40d413a9e07b |
line wrap: on
line source
NOTES ON THE EMACS BUG TRACKER -*- outline -*- The Emacs Bug Tracker can be found at http://emacsbugs.donarmstrong.com/ For a list of all bugs, see http://emacsbugs.donarmstrong.com/emacs ** 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. Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a mail with the bug report number in. ** To not get acknowledgement mail from the tracker, add an "X-Debbugs-No-Ack:" header (with any value). ** To record a bug in the tracker without sending mail to the bug list. This can be useful to make a note of something discussed on emacs-devel that needs fixing. In other words, this can be the equivalent of adding something to FOR-RELEASE. To: quiet@emacsbugs.donarmstrong.com [headers end] Package: emacs Version: 23.0.60 Severity: minor Remember to fix FOO, as discussed on emacs-devel at http://... . ** 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 ** How to avoid multiple copies of mails. When you reply to a bug, respect the Reply-To address, ie send mail only to the submitter address and the numbered bug address. Do not send mail direct to bug-gnu-emacs or emacs-pretest-bug unless you are reporting a new bug. ** To close bug #123 (for example), send mail To: 123-done@emacsbugs.donarmstrong.com with a brief explanation in the body as to why the bug was closed. ** To reopen a closed bug #123: To: control@emacsbugs.donarmstrong.com reopen 123 thanks ** quit|stop|thank|thanks|thankyou|thank you On a line by itself, this tells the control server to ignore the rest of the message. ** Bugs can be tagged in various ways (eg wontfix, patch, etc). For a list of available tags, see: http://emacsbugs.donarmstrong.com/Developer#tags ** To tag bug #123 (for example), send a mail of the form: To: control@emacsbugs.donarmstrong.com tags 123 wontfix thanks Or just add the tags 123 wontfix thanks at the beginning of a reply. The tag can be prefixed with +, - or =, meaning to add (the default), remove, or reset the tags. ** To remove spam from the tracker, move it to the `spam' pseudo-package: To: control@emacsbugs.donarmstrong.com reassign 123 spam thanks ** To merge bugs: Eg when bad replies create a bunch of new bugs for the same report. Bugs must all be in the same state. To: control@emacsbugs.donarmstrong.com merge 123 124 125 ... ** To set severity: To: control@emacsbugs.donarmstrong.com severity 123 critical|grave|serious|important|normal|minor|wishlist See http://emacsbugs.donarmstrong.com/Developer#severities for the meanings. ** To set the onwer of a bug: To: control@emacsbugs.donarmstrong.com owner 123 A Hacker <none@example.com> The shorthand `!' means your own address. ** To mark a bug as fixed in a particular version: To: control@emacsbugs.donarmstrong.com fixed 123 23.0.60