procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

*** empty log message ***

Browse source
This commit is contained in:
Glenn Morris 2008-07-04 19:32:56 +00:00
parent d7c664f351
commit cbed6befa5
1 changed files with 13 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
admin/notes/bugtracker
View file

@ -66,8 +66,9 @@ quit|stop|thank|thanks|thankyou|thank you
The control server ignores anything after the last line above. So you
can place control commands at the beginning of a reply to a bug
report, and Cc: the control server (note the commands have no effect
if you just send them to the bug-report number).
report, and Bcc: the control server (note the commands have no effect
if you just send them to the bug-report number). Bcc: is better than Cc:
in case people use Reply-to-All in response.
Some useful control commands:
@ -75,12 +76,14 @@ Some useful control commands:
reopen 123
*** Bugs can be tagged in various ways (eg wontfix, patch, etc).
For a list of available tags, see:
http://emacsbugs.donarmstrong.com/Developer#tags
The tag can be prefixed with +, - or =, meaning to add (the default),
remove, or reset the tags. E.g.:
The available tags are:
patch wontfix moreinfo unreproducible fixed notabug
Note that the list at http://emacsbugs.donarmstrong.com/Developer#tags
is incorrect, at least for Emacs.
The list of tags can be prefixed with +, - or =, meaning to add (the
default), remove, or reset the tags. E.g.:
tags 123 +wontfix
tags 123 + wontfix
*** To merge bugs:
Eg when bad replies create a bunch of new bugs for the same report.
@ -107,5 +110,8 @@ The shorthand `!' means your own address.
*** To mark a bug as fixed in a particular version:
fixed 123 23.0.60
*** To remove a "fixed" mark:
notfixed 123 23.0.60
** To remove spam from the tracker, move it to the `spam' pseudo-package:
reassign 123 spam