X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2Fserver-control.html.in;h=95649cc54d886a20cc9325494d436943f1251f19;hb=14a0ebc67f8b2510e7ca09d3298f23469bd03c32;hp=d46c2670d0a530ad727a185acbcb9f4e923ace27;hpb=d3a09e475d68f3cd305505b7514309f05e8d486f;p=debbugs.git diff --git a/html/server-control.html.in b/html/server-control.html.in index d46c267..95649cc 100644 --- a/html/server-control.html.in +++ b/html/server-control.html.in @@ -3,7 +3,9 @@ $gControlHtml = < $gProject $gBug system - control mail server commands + + @@ -91,6 +93,12 @@ mailservers is available via the WWW, in the $gBug is cleared. This is identical to the behaviour of reopen. +

This command will only cause a bug to be marked as not done if no + version is specified, or if the version being marked found + is equal to the version which was last marked fixed. (If + you are certain that you want the bug marked as not done, + use reopen in conjunction with found.

+

This command was introduced in preference to reopen because it was difficult to add a version to that command's syntax without suffering ambiguity. @@ -150,7 +158,7 @@ mailservers is available via the WWW, in

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

clone bugnumber [ new IDs ] +
clone bugnumber NewID [ 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 @@ -202,6 +210,12 @@ mailservers is available via the WWW, in

Merged reports are all expired simultaneously, and only when all of the reports each separately meet the criteria for expiry. +

forcemerge bugnumber bugnumber ... +
Forcibly merges two or more $gBug reports. The first bug is + chosen as the master bug, and its seetings are assigned to the bugs + listed next in the command. See the text above for a description of + what merging means. +
unmerge bugnumber
Disconnects a $gBug report from any other reports with which it may have @@ -256,6 +270,22 @@ mailservers is available via the WWW, in

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

block|unblock bugnumber by|with bug [ bug ... ] + +
Use to note that one bug blocks another bug from being fixed. + The first listed bug is the one being blocked, and it is followed + by the bug or bugs that are blocking it. Use unblock + to unblock a bug. + +

Example usage:

+ + 
+        # indicates that 7890 cannot be fixed until 123456 is fixed
+        block 7890 by 123456
+        # indicates that 7890 can be fixed before 123456 after all
+        unblock 7890 by 123456
+
+
close bugnumber [ fixed-version ] (deprecated) @@ -297,8 +327,8 @@ mailservers is available via the WWW, in
owner bugnumber address | !
Sets address to be the "owner" of #bugnumber. - The owner of a $gBug claims responsibility for fixing it and will receive - all mail regarding it. This is useful to share out work in cases where a + The owner of a $gBug claims responsibility for fixing it. + This is useful to share out work in cases where a package has a team of maintainers.

If you wish to become the owner of the $gBug yourself, you can use the @@ -309,6 +339,18 @@ mailservers is available via the WWW, in

Forgets any idea that the $gBug has an owner other than the usual maintainer. If the $gBug had no owner recorded then this will do nothing. +
archive bugnumber + +
Archives a $gBug that was previously archived if the $gBug + fulfills the requirements for archival, ignoring time. + +
unarchive bugnumber + +
Unarchives a $gBug that was previously archived. Unarchival + should generally be coupled with reopen and found/fixed as + approprite. Bugs that have been unarchived can be archived using + archive assuming the non-time based archival requirements are met. +
#...
One-line comment. The # must be at the start of the line. @@ -318,12 +360,20 @@ mailservers is available via the WWW, in
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. +
thank +
thanks +
thankyou +
thank you +
-- + + + + +
On a line by itself, in any case, possibly followed by + whitespace, 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.