aboutsummaryrefslogtreecommitdiffstats
path: root/admin
diff options
context:
space:
mode:
authorMark A. Hershberger2010-01-24 23:52:26 -0500
committerMark A. Hershberger2010-01-24 23:52:26 -0500
commitb1bb0a2570b8a40017220097c40c6057cfe17efe (patch)
treed308182f02f1d459ea9a21c31a8ca8b0f3b4f787 /admin
parentaaef4f91fad60716fa070b912d71b9f1ccd2e7b4 (diff)
parent8dc1adf681df162bfd305debef0e1ab31bed3ebd (diff)
downloademacs-b1bb0a2570b8a40017220097c40c6057cfe17efe.tar.gz
emacs-b1bb0a2570b8a40017220097c40c6057cfe17efe.zip
merge conflict
Diffstat (limited to 'admin')
-rw-r--r--admin/ChangeLog5
-rw-r--r--admin/notes/bugtracker89
-rwxr-xr-xadmin/revdiff137
3 files changed, 60 insertions, 171 deletions
diff --git a/admin/ChangeLog b/admin/ChangeLog
index 8fd3b828a71..a43dbe931f0 100644
--- a/admin/ChangeLog
+++ b/admin/ChangeLog
@@ -1,3 +1,8 @@
12010-01-20 Glenn Morris <rgm@gnu.org>
2
3 * revdiff: Remove file that only works with CVS, and isn't really
4 needed with Bazaar (given the in-built revision options of bzr diff).
5
12010-01-12 Glenn Morris <rgm@gnu.org> 62010-01-12 Glenn Morris <rgm@gnu.org>
2 7
3 * emacs-pretesters, make-announcement: Use bug-gnu-emacs rather 8 * emacs-pretesters, make-announcement: Use bug-gnu-emacs rather
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index e253cb6d1b4..1a9f6f2bd4c 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -35,15 +35,16 @@ So you need to explicitly CC him/her (and anyone else you like).
35(Many people think the submitter SHOULD be automatically subscribed 35(Many people think the submitter SHOULD be automatically subscribed
36to subsequent discussion, but this does not seem to be implemented. 36to subsequent discussion, but this does not seem to be implemented.
37See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078) 37See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078)
38See also http://debbugs.gnu.org/5439
38 39
39Do NOT send a separate copy to the bug list, since this may generate a 40Do NOT send a separate copy to the bug list address, since this may
40new report. The only time to send mail to the bug list is to create a 41generate a new report. The only time to send mail to the bug list
41new report. 42address is to create a new report.
42 43
43Gnus users can add the following to message-dont-reply-to-names; 44Gnus users can add the following to message-dont-reply-to-names;
44similarly with Rmail and rmail-dont-reply-to-names: 45similarly with Rmail and rmail-dont-reply-to-names:
45 46
46"\\(emacs-pretest-bug\\|bug-gnu-emacs\\)@gnu\\.org\\|\ 47"\\(emacs-pretest-bug\\|bug-gnu-emacs\\|bug-\\(e\\|gnu\\)macs\\)@gnu\\.org\\|\
47\\(submit\\|control\\|owner\\)@debbugs\\.gnu\\.org" 48\\(submit\\|control\\|owner\\)@debbugs\\.gnu\\.org"
48 49
49The "owner@debbugs.gnu.org" entry is there because it appears in the 50The "owner@debbugs.gnu.org" entry is there because it appears in the
@@ -58,27 +59,23 @@ reporting.)
58(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. 59(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
59Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a 60Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a
60mail with the bug report number in. If you do not do this, each reply 61mail with the bug report number in. If you do not do this, each reply
61in the subsequent discussion will end up creating a new bug. This is 62in the subsequent discussion will end up creating a new bug.
62annoying. 63This is annoying.
63 64
64Note that the way this feature works is perhaps not ideal (Bug#1720). 65If a new report contains X-Debbugs-CC in the input, this is
65If X-Debbugs-CC: was specifed by a real header, that header is removed 66converted to a real Cc header in the output. (See Bug#1720).
66in the mail sent out to the bug list, and the addresses merged into 67It is also merged into the Resent-CC header (see below).
67the Resent-CC header (see below). They don't appear as an explicit CC:
68header, nor do they appear in the Reply-To: header. So people you
69X-Debbugs-CC are not included in any following discussion unless they are
70manually cc'd. So this feature really only serves to notify them that
71a bug has been filed. It's then up to them to follow any subsequent
72discussion.
73
74If X-Debbugs-CC were merged into the Reply-To header, this might work
75more the way people expect.
76 68
77** How does Debbugs send out mails? 69** How does Debbugs send out mails?
78 70
79The mails are sent out to the bug list with From: and To: unchanged. 71The mails are sent out to the bug list by being resent. The From:
80Eg if you file a bug with "submit@debbugs.gnu.org", that 72header is unchanged. In new reports only (at present), the To:
81remains in the To: address. They reach the bug list by being resent. 73address is altered as follows. Any "bug-gnu-emacs",
74"emacs-pretest-bug", or "submit@debbugs" address is replaced by
75123@debbugs in the mail that gets sent out. (This also applies to any
76Cc: header, though you should be using X-Debbugs-CC instead in new
77reports). The original header is stored as X-Debbugs-Original-To, if
78it was changed. Any X-Debbugs-CC is merged into the Cc.
82 79
83Mails arriving at the bug list have the following Resent-* headers: 80Mails arriving at the bug list have the following Resent-* headers:
84 81
@@ -88,10 +85,6 @@ Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries
88 85
89The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. 86The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases.
90 87
91A new report also has:
92
93Mail-Followup-To: bug submitter, 123@debbugs.gnu.org
94
95** To not get acknowledgement mail from the tracker, 88** To not get acknowledgement mail from the tracker,
96add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, 89add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus,
97you can add an element to gnus-posting-styles to do this automatically, eg: 90you can add an element to gnus-posting-styles to do this automatically, eg:
@@ -124,10 +117,10 @@ When you close a bug, you get a message matching:
124^X-Emacs-PR-Message: closed 117^X-Emacs-PR-Message: closed
125 118
126** How to avoid multiple copies of mails. 119** How to avoid multiple copies of mails.
127When you reply to a bug, respect the Reply-To address, ie send mail 120If you reply to reports in the normal way, this should work fine.
128only to the submitter address and the numbered bug address. Do not 121Basically, reply only to the numbered bug address (and any individual
129send mail direct to bug-gnu-emacs or emacs-pretest-bug unless you are 122people's addresses). Do not send mail direct to bug-gnu-emacs or
130reporting a new bug. 123emacs-pretest-bug unless you are reporting a new bug.
131 124
132** To close bug #123 (for example), send mail 125** To close bug #123 (for example), send mail
133 126
@@ -195,8 +188,7 @@ tag:tag # all bugs with given tag
195See <http://wiki.debian.org/bugs.debian.org/usertags> 188See <http://wiki.debian.org/bugs.debian.org/usertags>
196 189
197"Usertags" are very similar to tags: a set of labels that can be added 190"Usertags" are very similar to tags: a set of labels that can be added
198to a bug. There are two differences between normal tags and user 191to a bug. There are two differences between normal tags and user tags:
199tags:
200 192
2011) Anyone can define any valid usertag they like. In contrast, only a 1931) Anyone can define any valid usertag they like. In contrast, only a
202limited, predefined set of normal tags are available (see above). 194limited, predefined set of normal tags are available (see above).
@@ -362,7 +354,7 @@ bug number.
362 354
363Similarly, when you close a bug, it can be helpful to include the 355Similarly, when you close a bug, it can be helpful to include the
364relevant ChangeLog entry in the message to the bug tracker, so people 356relevant ChangeLog entry in the message to the bug tracker, so people
365can see eaxctly what the fix was. 357can see exactly what the fix was.
366 358
367*** bug-reference-mode 359*** bug-reference-mode
368 360
@@ -373,6 +365,17 @@ the bug web-pages.
373 365
374http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html 366http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
375 367
368** Bazaar stuff
369
370*** You can use `bzr commit --fixes emacs:123' to mark that a commit fixes
371Emacs bug 123. You will first need to add a line to your bazaar.conf
372(untested):
373
374bugtracker_emacs_url = http://debbugs.gnu.org/{id}
375
376Note that all this does is add some metadata to the commit, it doesn't
377actually mark the bug as closed in the tracker.
378
376** Gnus-specific voodoo 379** Gnus-specific voodoo
377 380
378*** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group 381*** Put point on a bug-number and try: M-x gnus-read-ephemeral-emacs-bug-group
@@ -448,7 +451,10 @@ needlessly held for moderation:
448*** debbugs-submit 451*** debbugs-submit
449(quiet|control|submit)@(debbugs\.gnu\.org|emacsbugs\.donarmstrong\.com) 452(quiet|control|submit)@(debbugs\.gnu\.org|emacsbugs\.donarmstrong\.com)
450[0-9]+(-done|-quiet|-subscribe)?@(debbugs\.gnu\.org|emacsbugs\.donarmstrong\.com) 453[0-9]+(-done|-quiet|-subscribe)?@(debbugs\.gnu\.org|emacsbugs\.donarmstrong\.com)
451(bug-gnu-emacs|emacs-pretest-bug)@gnu\.org 454(bug-gnu-emacs|emacs-pretest-bug|bug-(e|gnu)macs)@gnu\.org
455
456bug-emacs and bug-gnumacs are lesser-used aliases from fencepost's
457/etc/aliases file.
452 458
453*** emacs-bug-tracker 459*** emacs-bug-tracker
454sender: bug-gnu-emacs AT gnu.org 460sender: bug-gnu-emacs AT gnu.org
@@ -456,3 +462,18 @@ recipient: emacs-bug-tracker AT debbugs\.gnu\.org
456 462
457The latter is because that is the address that debbugs actually sends to. 463The latter is because that is the address that debbugs actually sends to.
458An /etc/aliases entry redirects it to the real emacs-bug-tracker address. 464An /etc/aliases entry redirects it to the real emacs-bug-tracker address.
465
466** Administrivia
467
468The debbugs-submit list should have the administrivia option off,
469else it can by mistake filter out requests to subscribe to bugs.
470But, this feature doesn't work anyway (see bug#5439).
471
472** How to test changes
473
474Add an entry to /etc/debbugs/Maintainers like:
475
476mytest my.email.address
477
478Then if you do all your testing with 'Package: mytest', the resulting
479mails should only go to your email address.
diff --git a/admin/revdiff b/admin/revdiff
deleted file mode 100755
index 7a1e93a64fe..00000000000
--- a/admin/revdiff
+++ /dev/null
@@ -1,137 +0,0 @@
1#! /usr/bin/perl
2
3# Copyright (C) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
4# 2010 Free Software Foundation, Inc.
5#
6# This file is part of GNU Emacs.
7
8# GNU Emacs is free software: you can redistribute it and/or modify
9# it under the terms of the GNU General Public License as published by
10# the Free Software Foundation, either version 3 of the License, or
11# (at your option) any later version.
12
13# GNU Emacs is distributed in the hope that it will be useful,
14# but WITHOUT ANY WARRANTY; without even the implied warranty of
15# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16# GNU General Public License for more details.
17
18# You should have received a copy of the GNU General Public License
19# along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
20
21
22use File::Basename;
23
24if (@ARGV < 3)
25{
26 print <<USAGE;
27revdiff FILE OLD NEW
28
29Get a diff of FILE between revisions OLD and NEW. Store the
30diff in a file named FILE-OLD-NEW.diff.
31
32If OLD is `-' use FILE's current revision for OLD. If OLD is
33`-<number>', use the Nth revision before the current one for OLD.
34
35If NEW is +<number> or -<number>, build diffs between revisions OLD
36and OLD +/- <number>.
37
38Examples:
39
40revdiff FILE - -1 get the latest change of FILE
41revdiff FILE -1 +1 also gets the latest change of FILE
42revdiff FILE 1.500 +2 get diffs 1.500-1.501 and 1.501-1.502.
43
44USAGE
45 exit 1;
46}
47
48$file = shift @ARGV;
49$old = shift @ARGV;
50
51sub diffit
52{
53 my ($old, $new) = @_;
54 print "cvs diff -r$old -r$new $file >$file-$old-$new.diff\n";
55 system "cvs diff -r$old -r$new $file >$file-$old-$new.diff";
56}
57
58sub current_revision ($)
59{
60 my ($file) = @_;
61 my $dir = dirname ($file);
62 my $base = basename ($file);
63 my $entries = "$dir/CVS/Entries";
64 die "Can't find $entries" unless -f $entries;
65 open (IN, "<$entries") or die "Cannot open $entries";
66 my $rev;
67 while ($line = <IN>)
68 {
69 if ($line =~ m,/$base/([^/]+),)
70 {
71 $rev = $1;
72 break;
73 }
74 }
75 die "Cannot determine current revision of $file" unless $rev;
76 close (IN);
77 return $rev;
78}
79
80if ($old eq "-")
81 {
82 $old = current_revision ($file);
83 }
84elsif ($old =~ /^-(\d+)$/)
85 {
86 my $offset = $1;
87 $old = current_revision ($file);
88 die "Internal error" unless $old =~ /(.*)\.(\d+)$/;
89 my $minor = $2 - $offset;
90 $old = sprintf ("%d.%d", $1, $minor);
91 }
92
93while (@ARGV)
94 {
95 my $new = shift @ARGV;
96 if ($new =~ /^[+]\d+$/)
97 {
98 my $n = $new;
99 for ($i = 0; $i < $n; ++$i)
100 {
101 unless ($old =~ /(.*)\.(\d+)$/)
102 {
103 die "Internal error";
104 }
105 my $j = $2 + 1;
106 $new = "$1.$j";
107 diffit ($old, $new);
108 $old = $new;
109 }
110 }
111 elsif ($new =~ /^[-]\d+$/)
112 {
113 my $n = - $new;
114 for ($i = 0; $i < $n; ++$i)
115 {
116 unless ($old =~ /(.*)\.(\d+)$/)
117 {
118 die "Internal error";
119 }
120 my $j = $2 - 1;
121 $new = "$1.$j";
122 diffit ($new, $old);
123 $old = $new;
124 }
125 }
126 else
127 {
128 diffit ($old, $new);
129 $old = $new;
130 }
131 }
132
133# Local Variables:
134# mode: cperl
135# End:
136
137# arch-tag: 2798b20d-c7f2-4c78-8378-7bb529c36a09