Mercurial > emacs

comparison admin/notes/bugtracker @ 107018:ee105028fee8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add some details of bzr's --fixes option.
author Glenn Morris <rgm@gnu.org>
date Wed, 27 Jan 2010 21:15:52 -0800
parents 001a0729d255
children fb827ff9ec83
comparison
equal deleted inserted replaced
107017:6e5747b7cfa2 107018:ee105028fee8
176 4) Send a copy of your mail to the bug-gnu-emacs list in exactly the 176 4) Send a copy of your mail to the bug-gnu-emacs list in exactly the
177 same way as if you had sent mail to "123" (sans -done). This mail has 177 same way as if you had sent mail to "123" (sans -done). This mail has
178 headers: 178 headers:
179 179
180 X-Emacs-PR-Message: cc-closed 123 180 X-Emacs-PR-Message: cc-closed 123
181 Mail-Followup-To: 123@debbugs.gnu.org, ... 181 Mail-Followup-To: 123@debbugs.gnu.org, person-who-closed
182 182
183 (This is Emacs-specific. Normally the bug list gets the same mail as in 3). 183 (This is Emacs-specific. Normally the bug list gets the same mail as in 3).
184 184
185 ** Setting bug parameters. 185 ** Setting bug parameters.
186 There are two ways to set the parameters of bugs in the database 186 There are two ways to set the parameters of bugs in the database
417 http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html 417 http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
418 418
419 ** Bazaar stuff 419 ** Bazaar stuff
420 420
421 *** You can use `bzr commit --fixes emacs:123' to mark that a commit fixes 421 *** You can use `bzr commit --fixes emacs:123' to mark that a commit fixes
422 Emacs bug 123. You will first need to add a line to your bazaar.conf 422 Emacs bug 123. You will first need to add a line to your bazaar.conf:
423 (untested):
424 423
425 bugtracker_emacs_url = http://debbugs.gnu.org/{id} 424 bugtracker_emacs_url = http://debbugs.gnu.org/{id}
426 425
427 Note that all this does is add some metadata to the commit, it doesn't 426 Note that all this does is add some metadata to the commit, it doesn't
428 actually mark the bug as closed in the tracker. 427 actually mark the bug as closed in the tracker. There seems to be no
428 way to see this "metadata" with `bzr log', which is rather poor, but
429 it will show up as a link in a recent loggerhead installation, or with
430 some of the graphical frontends to bzr log.
429 431
430 ** Gnus-specific voodoo 432 ** Gnus-specific voodoo
431 433
432 *** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group 434 *** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group
433 435