aboutsummaryrefslogtreecommitdiffstats
path: root/admin/notes
diff options
context:
space:
mode:
authorGlenn Morris2009-12-01 03:10:31 +0000
committerGlenn Morris2009-12-01 03:10:31 +0000
commitcf17679916b44005d79302008e34d8d2e390b6cb (patch)
tree24433e5b8da9351c85b7bdb9c42f593218bc2d69 /admin/notes
parentfb0c18ff8002ba005c2226dfe3bd9448e8b8ed1a (diff)
downloademacs-cf17679916b44005d79302008e34d8d2e390b6cb.tar.gz
emacs-cf17679916b44005d79302008e34d8d2e390b6cb.zip
Mention usertags.
Diffstat (limited to 'admin/notes')
-rw-r--r--admin/notes/bugtracker62
1 files changed, 62 insertions, 0 deletions
diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index 725831b4b45..ffd42b9f428 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -180,6 +180,68 @@ default), remove, or reset the tags. E.g.:
180 180
181tags 123 + wontfix 181tags 123 + wontfix
182 182
183** Usertags
184
185See <http://wiki.debian.org/bugs.debian.org/usertags>
186
187"Usertags" are very similar to tags: a set of labels that can be added
188to a bug. There are two differences between normal tags and user
189tags:
190
1911) Anyone can define any valid usertag they like. In contrast, only a
192limited, predefined set of normal tags are available (see above).
193
1942) A usertag is associated with a specific email address.
195
196You set usertags in the same way as tags, by talking to the control
197server. One difference is that you can also specify the associated
198email address. If you don't explicitly specify an address, then it
199will use the one from which you send the control message. The address
200must have the form of an email address (with an "@" sign and least 4
201characters after the "@").
202
203*** Setting usertags
204
205a) In a control message:
206
207user bug-gnu-emacs@gnu.org
208usertags 1234 any-tag-you-like
209
210This will add a usertag "any-tag-you-like" to bug 1234. The tag will
211be associated with the address "bug-gnu-emacs@gnu.org". If you omit
212the first line, the tag will be associated with your email address.
213
214The syntax of the usertags command is the same as that of tags (eg wrt
215the optional [=+-] argument).
216
217b) In an initial submission, in the pseudo-header:
218
219User: bug-gnu-emacs@gnu.org
220Usertags: a-new-tag
221
222Again, the "User" is optional.
223
224*** Searching by usertags
225
226The search interface is not as advanced as for normal tags. You need
227to construct the relevant url yourself rather than just typing in a
228search box. The only piece you really need to add is the "users"
229portion, the rest has the same syntax as normal.
230
231**** To find all bugs usertagged by a given email address:
232
233http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org
234
235(Supposedly, the "users" field can be a comma-separated list of more
236than one email address, but it does not seem to work for me.)
237
238**** To find bugs tagged with a specific usertag:
239
240This works just like a normal tags search, but with the addition of a
241"users" field. Eg:
242
243http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org;tag=calendar
244
183*** To merge bugs: 245*** To merge bugs:
184Eg when bad replies create a bunch of new bugs for the same report. 246Eg when bad replies create a bunch of new bugs for the same report.
185Bugs must all be in the same state (e.g. same package(s) and severity 247Bugs must all be in the same state (e.g. same package(s) and severity