Mercurial > emacs
annotate admin/notes/bugtracker @ 106611:09979dbce827
Refer to the static bug page (rather than the dynamic one) for a list
of all bugs.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Thu, 17 Dec 2009 04:22:45 +0000 |
parents | 033513eeca72 |
children | 8eda61c377f7 |
rev | line source |
---|---|
95505 | 1 NOTES ON THE EMACS BUG TRACKER -*- outline -*- |
95445 | 2 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
3 The Emacs Bug Tracker can be found at http://debbugs.gnu.org/ |
95445 | 4 |
106611
09979dbce827
Refer to the static bug page (rather than the dynamic one) for a list
Glenn Morris <rgm@gnu.org>
parents:
106610
diff
changeset
|
5 For a list of all bugs, see http://debbugs.gnu.org/db/pa/lemacs.html |
09979dbce827
Refer to the static bug page (rather than the dynamic one) for a list
Glenn Morris <rgm@gnu.org>
parents:
106610
diff
changeset
|
6 (this is a static page, updated once a day) |
95445 | 7 |
97973 | 8 ** How do I report a bug in Emacs now? |
9 The same way as you always did. Send mail to bug-gnu-emacs@gnu.org, | |
10 or use M-x report-emacs-bug. | |
11 | |
12 The only differences are: | |
13 | |
14 i) Your report will be assigned a number and generate an automatic reply. | |
15 | |
16 ii) Optionally, you can set some database parameters when you first | |
17 report a bug (see "Setting bug parameters" below). | |
18 | |
98568 | 19 iii) If you want to CC: someone, use X-Debbugs-CC: (this is important; |
20 see below). | |
97973 | 21 |
22 Once your report is filed and assigned a number, it is sent out to the | |
23 bug mailing list. In some cases, it may be appropriate to just file a | |
24 bug, without sending out a copy. To do this, send mail to | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
25 quiet@debbugs.gnu.org. |
97973 | 26 |
27 ** How do I reply to an existing bug report? | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
28 Reply to 123@debbugs.gnu.org, replacing 123 with the number |
98513 | 29 of the bug you are interested in. NB this only sends mail to the |
30 bug-list, it does NOT (?) send a CC to the original bug submitter. | |
31 So you need to explicitly CC him/her (and anyone else you like). | |
32 | |
33 (Many people think the submitter SHOULD be automatically subscribed | |
34 to subsequent discussion, but this does not seem to be implemented. | |
35 See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078) | |
36 | |
37 Do NOT send a separate copy to the bug list, since this may generate a | |
38 new report. The only time to send mail to the bug list is to create a | |
39 new report. | |
95445 | 40 |
101597
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
41 Gnus users can add the following to message-dont-reply-to-names; |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
42 similarly with Rmail and rmail-dont-reply-to-names: |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
43 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
44 [FIXME needs updating for debbugs.gnu.org] |
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
45 |
101597
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
46 "\\(emacs-pretest-bug\\|bug-gnu-emacs\\)@gnu\\.org\\|\ |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
47 \\(\\(submit\\|control\\|owner\\)@emacsbugs\\.\\|bug-submit-list@\\)\ |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
48 donarmstrong\\.com" |
101512
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
49 |
101597
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
50 The "bug-submit-list@donarmstrong.com" and |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
51 "owner@debbugs.gnu.org" entries are there because they can |
101597
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
52 appear in the "Resent-To" and "Resent-CC" headers, respectively. For a |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
53 long time Rmail erroneously included these headers in replies. If you |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
54 correspond with an Rmail user on a bug, these addresses may end up in |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
55 the Cc. Mailing to them does nothing but create duplicates and errors. |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
56 (It is possible you might want to have a dialog with the owner |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
57 address, outside of normal bug reporting.) |
100191 | 58 |
96482 | 59 ** When reporting a bug, to send a Cc to another address |
98568 | 60 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. |
96482 | 61 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a |
98568 | 62 mail with the bug report number in. If you do not do this, each reply |
63 in the subsequent discussion will end up creating a new bug. This is | |
64 annoying. | |
95486 | 65 |
102276 | 66 Note that the way this feature works is perhaps not ideal (Bug#1720). |
67 If X-Debbugs-CC: was specifed by a real header, that header is removed | |
68 in the mail sent out to the bug list, and the addresses merged into | |
69 the Resent-CC header (see below). They don't appear as an explicit CC: | |
70 header, nor do they appear in the Reply-To: header. So people you | |
71 X-Debbugs-CC are not included in any following discussion unless they are | |
72 manually cc'd. So this feature really only serves to notify them that | |
73 a bug has been filed. It's then up to them to follow any subsequent | |
74 discussion. | |
75 | |
76 If X-Debbugs-CC were merged into the Reply-To header, this might work | |
77 more the way people expect. | |
78 | |
79 ** How does Debbugs send out mails? | |
80 | |
81 The mails are sent out to the bug list with From: and To: unchanged. | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
82 Eg if you file a bug with "submit@debbugs.gnu.org", that |
102276 | 83 remains in the To: address. They reach the bug list by being resent. |
84 | |
85 Mails arriving at the bug list have the following Resent-* headers: | |
86 | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
87 [ FIXME needs updating for debbugs.gnu.org ] |
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
88 |
102276 | 89 Resent-From: person who submitted the bug |
90 Resent-To: bug-submit-list@donarmstrong.com | |
91 Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries | |
92 | |
93 The "maintainer email address" is "Emacs Bugs <bug-gnu-emacs@gnu.org>" | |
94 in most cases. | |
95 | |
96 They also have: | |
97 | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
98 Reply-To: bug submitter, 123@debbugs.gnu.org |
102276 | 99 |
95505 | 100 ** To not get acknowledgement mail from the tracker, |
98513 | 101 add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, |
102 you can add an element to gnus-posting-styles to do this automatically, eg: | |
103 | |
104 ("gnu-emacs\\(-pretest\\)?-bug" | |
105 ("X-Debbugs-No-Ack" "yes")) | |
106 | |
107 (adjust the regexp according to the name you use for the bug lists) | |
95486 | 108 |
96467 | 109 ** To record a bug in the tracker without sending mail to the bug list. |
110 This can be useful to make a note of something discussed on | |
96468 | 111 emacs-devel that needs fixing. In other words, this can be the |
112 equivalent of adding something to FOR-RELEASE. | |
96467 | 113 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
114 To: quiet@debbugs.gnu.org |
96467 | 115 [headers end] |
116 Package: emacs | |
117 Version: 23.0.60 | |
118 Severity: minor | |
119 | |
120 Remember to fix FOO, as discussed on emacs-devel at http://... . | |
121 | |
96401 | 122 ** Not interested in tracker control messages (tags being set, etc)? |
123 Discard mails matching: | |
124 | |
125 ^X-Emacs-PR-Message: transcript | |
126 | |
96402 | 127 When you close a bug, you get a message matching: |
128 | |
129 ^X-Emacs-PR-Message: closed | |
130 | |
96401 | 131 ** How to avoid multiple copies of mails. |
132 When you reply to a bug, respect the Reply-To address, ie send mail | |
133 only to the submitter address and the numbered bug address. Do not | |
134 send mail direct to bug-gnu-emacs or emacs-pretest-bug unless you are | |
135 reporting a new bug. | |
136 | |
95505 | 137 ** To close bug #123 (for example), send mail |
95486 | 138 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
139 To: 123-done@debbugs.gnu.org |
95445 | 140 |
141 with a brief explanation in the body as to why the bug was closed. | |
106005
d44e34269048
No need to cc on -done messages.
Glenn Morris <rgm@gnu.org>
parents:
104535
diff
changeset
|
142 There is no need to cc the address without the "-done" part or the |
d44e34269048
No need to cc on -done messages.
Glenn Morris <rgm@gnu.org>
parents:
104535
diff
changeset
|
143 submitter; they get copies anyway so this will just result in more |
d44e34269048
No need to cc on -done messages.
Glenn Morris <rgm@gnu.org>
parents:
104535
diff
changeset
|
144 duplicate mail. |
95445 | 145 |
96482 | 146 ** Setting bug parameters. |
147 There are two ways to set the parameters of bugs in the database | |
148 (tags, severity level, etc). When you report a new bug, you can | |
149 provide a "pseudo-header" at the start of the report, eg: | |
95445 | 150 |
96482 | 151 Package: emacs |
152 Version: 23.0.60 | |
153 Severity: minor | |
95505 | 154 |
97973 | 155 Optionally, add a sub-package, eg Package: emacs,calendar. |
97782 | 156 This can include tags. Some things (e.g. submitter) don't seem to |
157 work here. | |
158 | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
159 Otherwise, send mail to the control server, control@debbugs.gnu.org. |
96482 | 160 At the start of the message body, supply the desired commands, one per |
161 line: | |
95505 | 162 |
96482 | 163 command bug-number [arguments] |
164 ... | |
165 quit|stop|thank|thanks|thankyou|thank you | |
95473 | 166 |
96482 | 167 The control server ignores anything after the last line above. So you |
168 can place control commands at the beginning of a reply to a bug | |
96506 | 169 report, and Bcc: the control server (note the commands have no effect |
170 if you just send them to the bug-report number). Bcc: is better than Cc: | |
171 in case people use Reply-to-All in response. | |
95473 | 172 |
96482 | 173 Some useful control commands: |
174 | |
175 *** To reopen a closed bug: | |
176 reopen 123 | |
177 | |
178 *** Bugs can be tagged in various ways (eg wontfix, patch, etc). | |
96506 | 179 The available tags are: |
180 patch wontfix moreinfo unreproducible fixed notabug | |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
181 Note that the list at http://debbugs.gnu.org/Developer#tags |
96506 | 182 is incorrect, at least for Emacs. |
183 The list of tags can be prefixed with +, - or =, meaning to add (the | |
184 default), remove, or reset the tags. E.g.: | |
95445 | 185 |
96506 | 186 tags 123 + wontfix |
95505 | 187 |
106337 | 188 ** Usertags |
189 | |
190 See <http://wiki.debian.org/bugs.debian.org/usertags> | |
191 | |
192 "Usertags" are very similar to tags: a set of labels that can be added | |
193 to a bug. There are two differences between normal tags and user | |
194 tags: | |
195 | |
196 1) Anyone can define any valid usertag they like. In contrast, only a | |
197 limited, predefined set of normal tags are available (see above). | |
198 | |
199 2) A usertag is associated with a specific email address. | |
200 | |
201 You set usertags in the same way as tags, by talking to the control | |
202 server. One difference is that you can also specify the associated | |
203 email address. If you don't explicitly specify an address, then it | |
204 will use the one from which you send the control message. The address | |
205 must have the form of an email address (with an "@" sign and least 4 | |
206 characters after the "@"). | |
207 | |
208 *** Setting usertags | |
209 | |
210 a) In a control message: | |
211 | |
212 user bug-gnu-emacs@gnu.org | |
213 usertags 1234 any-tag-you-like | |
214 | |
215 This will add a usertag "any-tag-you-like" to bug 1234. The tag will | |
216 be associated with the address "bug-gnu-emacs@gnu.org". If you omit | |
217 the first line, the tag will be associated with your email address. | |
218 | |
219 The syntax of the usertags command is the same as that of tags (eg wrt | |
220 the optional [=+-] argument). | |
221 | |
222 b) In an initial submission, in the pseudo-header: | |
223 | |
224 User: bug-gnu-emacs@gnu.org | |
225 Usertags: a-new-tag | |
226 | |
227 Again, the "User" is optional. | |
228 | |
229 *** Searching by usertags | |
230 | |
231 The search interface is not as advanced as for normal tags. You need | |
232 to construct the relevant url yourself rather than just typing in a | |
233 search box. The only piece you really need to add is the "users" | |
234 portion, the rest has the same syntax as normal. | |
235 | |
236 **** To find all bugs usertagged by a given email address: | |
237 | |
238 http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org | |
239 | |
240 (Supposedly, the "users" field can be a comma-separated list of more | |
241 than one email address, but it does not seem to work for me.) | |
242 | |
243 **** To find bugs tagged with a specific usertag: | |
244 | |
245 This works just like a normal tags search, but with the addition of a | |
246 "users" field. Eg: | |
247 | |
248 http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org;tag=calendar | |
249 | |
96482 | 250 *** To merge bugs: |
251 Eg when bad replies create a bunch of new bugs for the same report. | |
104535
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
252 Bugs must all be in the same state (e.g. same package(s) and severity |
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
253 -- see `reassign' and `severity' below), but need not have the same |
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
254 tags (tags are merged). E.g.: |
95505 | 255 |
96482 | 256 merge 123 124 125 ... |
96389 | 257 |
97989 | 258 Note that merging does not affect titles. In particular, a "retitle" |
259 of merged bugs only affects individual bugs, not all of them. | |
260 | |
96482 | 261 *** Forcing a merge: |
97989 | 262 Like `merge', but bugs need not be in the same state. The packages |
104535
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
263 must still match though (see `reassign' below). The first one listed |
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
264 is the master. E.g.: |
96469 | 265 |
96482 | 266 forcemerge 123 124 125 ... |
96469 | 267 |
100191 | 268 Note: you cannot merge with an archived bug - you must unarchive it first. |
269 | |
97713 | 270 *** To unmerge bugs: |
271 To disconnect a bug from all bugs it is merged with: | |
272 | |
273 unmerge 123 | |
274 | |
275 This command accepts only one bug number. | |
276 | |
98523 | 277 *** To clone bugs: |
278 Useful when one report refers to more than one bug. | |
279 | |
280 clone 123 -1 [-2 ...] | |
281 retitle -1 second bug | |
282 retitle -2 third bug | |
283 | |
284 The negative numbers provide a way to refer to the cloned bugs (which | |
285 will be assigned proper numbers). | |
286 | |
101763 | 287 NB you cannot clone a merged bug. You'd think that trying to do so |
288 would just give you an unmerged copy of the specified bug number, but no: | |
289 | |
290 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474742 | |
291 | |
292 You must unmerge, clone, then re-merge. | |
293 | |
96482 | 294 *** To set severity: |
295 severity 123 critical|grave|serious|important|normal|minor|wishlist | |
96389 | 296 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
297 See http://debbugs.gnu.org/Developer#severities for the meanings. |
96447 | 298 |
97931 | 299 *** To set the owner of a bug: |
96482 | 300 owner 123 A Hacker <none@example.com> |
96447 | 301 |
302 The shorthand `!' means your own address. | |
303 | |
97931 | 304 *** To remove the owner of a bug: |
305 noowner 123 | |
306 | |
96482 | 307 *** To mark a bug as fixed in a particular version: |
308 fixed 123 23.0.60 | |
96447 | 309 |
96506 | 310 *** To remove a "fixed" mark: |
311 notfixed 123 23.0.60 | |
312 | |
104535
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
313 *** To assign or reassign a bug to a package or list of packages: |
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
314 reassign 1234 emacs,cc-mode |
31a925451502
How to reassign a bug to a list of packages.
Eli Zaretskii <eliz@gnu.org>
parents:
102558
diff
changeset
|
315 |
96482 | 316 ** To remove spam from the tracker, move it to the `spam' pseudo-package: |
317 reassign 123 spam | |
97753 | 318 |
319 ** To change the title of a bug: | |
320 retitle 123 Some New Title | |
321 | |
322 ** To change the submitter address: | |
323 submitter 123 none@example.com | |
97782 | 324 |
325 Note that it does not seem to work to specify "Submitter:" in the | |
326 pseudo-header when first reporting a bug. | |
100967 | 327 |
328 ** How does archiving work? | |
329 You can still send mail to a bug after it is closed. After 28 days with | |
330 no activity, the bug is archived, at which point no more changes can | |
331 be made. If you try to send mail to the bug after that (or merge with | |
332 it), it will be rejected. To make any changes, you must unarchive it first: | |
333 | |
334 unarchive 123 | |
335 | |
336 The bug will be re-archived after the next 28 day period of no activity. | |
101312
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
337 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
338 ** The web-page with the list of bugs is slow to load |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
339 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
340 It's a function of the number of displayed bugs. You can speed things |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
341 up by only looking at the newest 100 bugs: |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
342 |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
343 http://debbugs.gnu.org/cgi-bin/pkgreport.cgi?newest=100;package=emacs |
101312
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
344 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
345 The above page is accessible from the "Options" section at the end of |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
346 the "main list of bugs" page. Select bugs "in package" = emacs; |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
347 "newest bugs" = 100. (I have no idea how you get to that Options |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
348 section without having to go through the bug list page first...) |
101597
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
349 |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
350 ** Mails to the bug tracker disappear |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
351 |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
352 Apparently it has some kind of spam filter that sometimes silently |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
353 discards valid mails. Adding a subject (pointless in control messages) |
fb07b238e55a
Update message-dont-reply-to-names section.
Glenn Morris <rgm@gnu.org>
parents:
101512
diff
changeset
|
354 may help. |
101949
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
355 |
102558
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
356 ** ChangeLog issues |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
357 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
358 *** When you fix a bug, it can be helpful to put the bug number in the |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
359 ChangeLog entry, for example: |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
360 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
361 * foo.el (foofunc): Fix the `foo' case. (Bug#123) |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
362 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
363 Then the relevant bug can be found for easy reference. If it's an |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
364 obvious fix (e.g. a typo), there's no need to clutter the log with the |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
365 bug number. |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
366 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
367 Similarly, when you close a bug, it can be helpful to include the |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
368 relevant ChangeLog entry in the message to the bug tracker, so people |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
369 can see eaxctly what the fix was. |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
370 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
371 *** bug-reference-mode |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
372 |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
373 Activate `bug-reference-mode' in ChangeLogs to get clickable links to |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
374 the bug web-pages. |
47e37f294247
Mention some ChangeLog issues.
Glenn Morris <rgm@gnu.org>
parents:
102276
diff
changeset
|
375 |
106113 | 376 *** Debian stuff |
377 | |
378 http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html | |
379 | |
101949
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
380 ** Gnus-specific voodoo |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
381 |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
382 *** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
383 |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
384 *** If the above is not available: |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
385 (add-hook 'gnus-article-mode-hook |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
386 (lambda () |
106610
033513eeca72
emacsbugs.donarmstrong.com -> debbugs.gnu.org throughout.
Glenn Morris <rgm@gnu.org>
parents:
106337
diff
changeset
|
387 (setq bug-reference-url-format "http://debbugs.gnu.org/%s") |
101949
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
388 (bug-reference-mode 1))) |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
389 |
3d4ab04238a6
Add some gnus stuff from emacs-devel.
Glenn Morris <rgm@gnu.org>
parents:
101763
diff
changeset
|
390 and you can click on the bug number in the subject header. |