aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes/bugtracker
diff options
context:
space:
mode:
authorGlenn Morris2009-03-14 20:29:40 +0000
committerGlenn Morris2009-03-14 20:29:40 +0000
commit15d0fd3a5ba4e9358f5d89363c78fe77daaa01e3 (patch)
tree9365828d43f6e529489c0272f0994e08b28fdfa2 /admin/notes/bugtracker
parent87ede499619b42c318851aadd7a0e09d62e058b1 (diff)
downloademacs-15d0fd3a5ba4e9358f5d89363c78fe77daaa01e3.tar.gz
emacs-15d0fd3a5ba4e9358f5d89363c78fe77daaa01e3.zip
Mention some ChangeLog issues.
Diffstat (limited to 'admin/notes/bugtracker')
-rw-r--r--admin/notes/bugtracker20
1 files changed, 20 insertions, 0 deletions
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index cc14f3c38dc..030e8f668b6 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -278,6 +278,26 @@ Apparently it has some kind of spam filter that sometimes silently
278discards valid mails. Adding a subject (pointless in control messages) 278discards valid mails. Adding a subject (pointless in control messages)
279may help. 279may help.
280 280
281** ChangeLog issues
282
283*** When you fix a bug, it can be helpful to put the bug number in the
284ChangeLog entry, for example:
285
286 * foo.el (foofunc): Fix the `foo' case. (Bug#123)
287
288Then the relevant bug can be found for easy reference. If it's an
289obvious fix (e.g. a typo), there's no need to clutter the log with the
290bug number.
291
292Similarly, when you close a bug, it can be helpful to include the
293relevant ChangeLog entry in the message to the bug tracker, so people
294can see eaxctly what the fix was.
295
296*** bug-reference-mode
297
298Activate `bug-reference-mode' in ChangeLogs to get clickable links to
299the bug web-pages.
300
281** Gnus-specific voodoo 301** Gnus-specific voodoo
282 302
283*** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group 303*** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group