From 2ae2f4981bf41d9681ecc5231929afe8c9fd410f Mon Sep 17 00:00:00 2001 From: cjwatson <> Date: Mon, 25 Nov 2002 17:35:38 -0800 Subject: [PATCH] [project @ 2002-11-25 17:35:38 by cjwatson] Sync with webwml, somewhat. --- html/server-control.html.in | 93 ++++++++++++++++++++++++++----------- 1 file changed, 67 insertions(+), 26 deletions(-) diff --git a/html/server-control.html.in b/html/server-control.html.in index b7e45b4..64a4bb6 100644 --- a/html/server-control.html.in +++ b/html/server-control.html.in @@ -12,41 +12,30 @@ $gControlHtml = <In addition to the mailserver on request\@$gEmailDomain which allows the retrieval of $gBug data and documentation by email, there is another server on control\@$gEmailDomain which -also allows $gBug reports to be manipulated in various ways. +also allows $gBug reports to be manipulated in various ways.

The control server works just like the request server, except that it has some additional commands; in fact, it's the same program. The two addresses are only separated to avoid users making mistakes and -causing problems while merely trying to request information. +causing problems while merely trying to request information.

Please see the introduction to the request server available on the World Wide Web, in the file -bug-maint-mailcontrol.txt, or by sending +bug-log-mailserver.txt, or by sending help to either mailserver, for details of the basics of operating the mailservers and the common commands available when -mailing either address. +mailing either address.

The reference card for the mailservers is available via the WWW, in bug-mailserver-refcard.txt or by email using the -refcard command). +refcard command.

-

Commands available only at the control mailserver

+

Commands available at the control mailserver

-
close bugnumber - -
Close $gBug report #bugnumber. - -

A notification is sent to the user who reported the $gBug, but (in - contrast to mailing bugnumber-done@$gEmailDomain) the - text of the mail which caused the $gBug to be closed is not - included in that notification. The maintainer who closes a report - should ensure, probably by sending a separate message, that the user - who reported the $gBug knows why it is being closed. -

reassign bugnumber package
Records that $gBug #${gBug}number is a $gBug in package. @@ -97,7 +86,7 @@ mailservers is available via the WWW, in
retitle bugnumber new-title
Changes the title of a $gBug report to that specified (the default is - the Subject mail header from the original report. + the Subject mail header from the original report).

Unlike most of the other $gBug-manipulation commands when used on one of a set of merged reports this will change the title of only the @@ -112,6 +101,30 @@ mailservers is available via the WWW, in

For their meanings please consult the general developers' documentation for the $gBug system. +

clone bugnumber [ new IDs ] + +
The clone control command allows you to duplicate a $gBug report. It is + useful in the case where a single report actually indicates that multiple + distinct $gBugs have occurred. "New IDs" are negative numbers, + separated by spaces, which may be used in subsequent control commands to + refer to the newly duplicated $gBugs. A new report is generated for each + new ID. + +

Example usage:

+ + 
+        clone 12345 -1 -2
+        reassign -1 foo
+        retitle -1 foo: foo sucks
+        reassign -2 bar
+        retitle -2 bar: bar sucks when used with foo
+        severity -2 wishlist
+        clone 123456 -2
+        reassign -2 foo
+        retitle -2 foo: foo sucks
+        merge -1 -2
+
+
merge bugnumber bugnumber ...
Merges two or more $gBug reports. When reports are merged opening, @@ -121,12 +134,12 @@ mailservers is available via the WWW, in

Before $gBugs can be merged they must be in exactly the same state: either all open or all closed, with the same forwarded-to upstream - author address or all not marked as forwarded, and all assigned to the + author address or all not marked as forwarded, all assigned to the same package or package(s) (an exact string comparison is done on the - package to which the $gBug is assigned). If they don't start out in the - same state you should use reassign, reopen - and so forth to make sure that they are before using - merge. + package to which the $gBug is assigned), and all of the same severity. + If they don't start out in the same state you should use + reassign, reopen and so forth to make sure + that they are before using merge.

If any of the $gBugs listed in a merge command is already merged with another $gBug then all the reports merged with any of the @@ -134,7 +147,7 @@ mailservers is available via the WWW, in is reflexive, transitive and symmetric.

Merging reports causes a note to appear on each report's logs; on the - WWW pages this is includes links to the other $gBugs. + WWW pages this includes links to the other $gBugs.

Merged reports are all expired simultaneously, and only when all of the reports each separately meet the criteria for expiry. @@ -164,12 +177,40 @@ mailservers is available via the WWW, in The default action is adding.

Available tags currently include patch, wontfix, - moreinfo, unreproducible, fixed, - and stable. + moreinfo, unreproducible, help, + pending, fixed, security, + upstream, potato, woody, + sarge, + sid and experimental.

For their meanings please consult the general developers' documentation for the $gBug system. +

close bugnumber + +
Close $gBug report #bugnumber. + +

A notification is sent to the user who reported the $gBug, but (in + contrast to mailing bugnumber-done@$gEmailDomain) the + text of the mail which caused the $gBug to be closed is not + included in that notification. The maintainer who closes a report + should ensure, probably by sending a separate message, that the user + who reported the $gBug knows why it is being closed. + The use of this command is therefore deprecated. + +

quit +
stop +
thank... +
--... + +
Tells the control server to stop processing the message; the remainder + of the message can include explanations, signatures or anything else, + none of it will be detected by the control server. + +
#... + +
One-line comment. The # must be at the start of the line. +
-- 2.39.2