view admin/notes/bugtracker @ 96436:de00a663995a

(hi-lock-regexp-history): Make it an obsolete alias to `regexp-history'. (hi-lock-face-history): Rename to `hi-lock-face-defaults' and make it an obsolete alias to it. (hi-lock-face-defaults): New variable renamed from `hi-lock-face-history'. (hi-lock-line-face-buffer, hi-lock-face-buffer) (hi-lock-face-phrase-buffer): Use `read-regexp' instead of `read-from-minibuffer'. Doc fix. (hi-lock-read-face-name): Replace `hi-lock-face-history' with `hi-lock-face-defaults'. Remove `mapcar (lambda (f) (cons f f))'. Set `hist' arg of `completing-read' to `face-name-history'. Put a list of default faces to `default' arg instead of `hist' arg.

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.
[e-mail]), 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).

** 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: [e-mail]

with a brief explanation in the body as to why the bug was closed.


** To reopen a closed bug #123:

  To: [e-mail]

  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: [e-mail]

  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: [e-mail]

  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: [e-mail]
  merge 123 124 125 ...

** To set severity:

  To: [e-mail]
  severity 123 critical|grave|serious|important|normal|minor|wishlist

See http://emacsbugs.donarmstrong.com/Developer#severities for the meanings.