Mercurial > emacs
comparison admin/notes/bugtracker @ 106845:eb0820fd350a
Some more pointless updates.
| author | Glenn Morris <rgm@gnu.org> |
|---|---|
| date | Thu, 14 Jan 2010 19:51:48 -0800 |
| parents | 30345c2102a5 |
| children | 721d9f911bd2 |
comparison
equal
deleted
inserted
replaced
| 106844:a4e8916048d4 | 106845:eb0820fd350a |
|---|---|
| 86 Resent-To: owner@debbugs.gnu.org | 86 Resent-To: owner@debbugs.gnu.org |
| 87 Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries | 87 Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries |
| 88 | 88 |
| 89 The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. | 89 The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. |
| 90 | 90 |
| 91 They also have: | 91 A new report also has: |
| 92 | 92 |
| 93 Reply-To: bug submitter, 123@debbugs.gnu.org | |
| 94 Mail-Followup-To: bug submitter, 123@debbugs.gnu.org | 93 Mail-Followup-To: bug submitter, 123@debbugs.gnu.org |
| 95 | 94 |
| 96 ** To not get acknowledgement mail from the tracker, | 95 ** To not get acknowledgement mail from the tracker, |
| 97 add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, | 96 add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, |
| 98 you can add an element to gnus-posting-styles to do this automatically, eg: | 97 you can add an element to gnus-posting-styles to do this automatically, eg: |
| 172 reopen 123 | 171 reopen 123 |
| 173 | 172 |
| 174 *** Bugs can be tagged in various ways (eg wontfix, patch, etc). | 173 *** Bugs can be tagged in various ways (eg wontfix, patch, etc). |
| 175 The available tags are: | 174 The available tags are: |
| 176 patch wontfix moreinfo unreproducible fixed notabug | 175 patch wontfix moreinfo unreproducible fixed notabug |
| 177 Note that the list at http://debbugs.gnu.org/Developer#tags | 176 See http://debbugs.gnu.org/Developer#tags |
| 178 is incorrect, at least for Emacs. | |
| 179 The list of tags can be prefixed with +, - or =, meaning to add (the | 177 The list of tags can be prefixed with +, - or =, meaning to add (the |
| 180 default), remove, or reset the tags. E.g.: | 178 default), remove, or reset the tags. E.g.: |
| 181 | 179 |
| 182 tags 123 + wontfix | 180 tags 123 + wontfix |
| 181 | |
| 182 ** URL shortcuts | |
| 183 | |
| 184 http://debbugs.gnu.org/... | |
| 185 | |
| 186 123 # given bug number | |
| 187 123;mbox=yes # mbox version of given bug | |
| 188 package # bugs in given package (don't use "emacs" - too many bugs!) | |
| 189 from:submitter@email.address | |
| 190 severity:severity # all bugs of given severity | |
| 191 tag:tag # all bugs with given tag | |
| 183 | 192 |
| 184 ** Usertags | 193 ** Usertags |
| 185 | 194 |
| 186 See <http://wiki.debian.org/bugs.debian.org/usertags> | 195 See <http://wiki.debian.org/bugs.debian.org/usertags> |
| 187 | 196 |
| 333 | 342 |
| 334 ** The web-page with the list of bugs is slow to load | 343 ** The web-page with the list of bugs is slow to load |
| 335 | 344 |
| 336 It's a function of the number of displayed bugs. You can speed things | 345 It's a function of the number of displayed bugs. You can speed things |
| 337 up by only looking at the newest 100 bugs: | 346 up by only looking at the newest 100 bugs: |
| 338 | |
| 339 http://debbugs.gnu.org/cgi-bin/pkgreport.cgi?newest=100;package=emacs | 347 http://debbugs.gnu.org/cgi-bin/pkgreport.cgi?newest=100;package=emacs |
| 340 | 348 |
| 341 The above page is accessible from the "Options" section at the end of | 349 Or use the static index: |
| 342 the "main list of bugs" page. Select bugs "in package" = emacs; | 350 http://debbugs.gnu.org/db/ix/full.html |
| 343 "newest bugs" = 100. (I have no idea how you get to that Options | |
| 344 section without having to go through the bug list page first...) | |
| 345 | |
| 346 ** Mails to the bug tracker disappear | |
| 347 | |
| 348 Apparently it has some kind of spam filter that sometimes silently | |
| 349 discards valid mails. Adding a subject (pointless in control messages) | |
| 350 may help. | |
| 351 | 351 |
| 352 ** ChangeLog issues | 352 ** ChangeLog issues |
| 353 | 353 |
| 354 *** When you fix a bug, it can be helpful to put the bug number in the | 354 *** When you fix a bug, it can be helpful to put the bug number in the |
| 355 ChangeLog entry, for example: | 355 ChangeLog entry, for example: |
