$gProject $gBug system - control mail server commands

X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2Fserver-control.html.in;h=95649cc54d886a20cc9325494d436943f1251f19;hb=14a0ebc67f8b2510e7ca09d3298f23469bd03c32;hp=04d01aad472ea210bc735f1abe3d444c3faa9b13;hpb=39b3aae6d9107c55ee81a4f5bd1ac1dc5019a686;p=debbugs.git diff --git a/html/server-control.html.in b/html/server-control.html.in index 04d01aa..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 + + @@ -37,6 +39,7 @@ mailservers is available via the WWW, in

reassign bugnumber package + [ version ]

Records that $gBug #${gBug}number is a $gBug in package. This can be used to set the package if the user forgot the @@ -44,6 +47,9 @@ mailservers is available via the WWW, in are sent to anyone (other than the usual information in the processing transcript). +

If you supply a version, the $gBug tracking system will note + that the $gBug affects that version of the newly-assigned package. +

reopen bugnumber [ originator-address | = | ! ] @@ -68,6 +74,45 @@ mailservers is available via the WWW, in use the submitter command; note that this will inform the original submitter of the change. + If the $gBug was recorded as being closed in a particular version of a + package but recurred in a later version, it is better to use the + found command instead. + +

found bugnumber [ version ] + +

Record that #bugnumber has been encountered in the given + version of the package to which it is assigned. + +

The $gBug tracking system uses this information, in conjunction with + fixed versions recorded when closing $gBugs, to display lists of $gBugs + open in various versions of each package. It considers a $gBug to be open + when it has no fixed version, or when it has been found more recently than + it has been fixed. + +

If no version is given, then the list of fixed versions for + 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. + +

notfound bugnumber version + +

Remove the record that #bugnumber was encountered in the + given version of the package to which it is assigned. + +

This differs from closing the $gBug at that version in that the $gBug + is not listed as fixed in that version either; no information about that + version will be known. It is intended for fixing mistakes in the record of + when a $gBug was found. +

submitter bugnumber originator-address | ! @@ -113,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 @@ -151,7 +196,8 @@ mailservers is available via the WWW, in 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. + that they are before using merge. Titles are not required + to match, and will not be affected by the 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 @@ -164,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 @@ -180,13 +232,33 @@ mailservers is available via the WWW, in command; if you want to disconnect more than one $gBug simply include several unmerge commands in your message. -

tags bugnumber [ + | - | = ] tag +

tags bugnumber [ + | - | = ] tag [ tag ... ] + +

Sets tags for the $gBug report #bugnumber. No notification + is sent to the user who reported the $gBug. Setting the action to + + means to add each given tag, - + means to remove each given tag, and = means to + ignore the current tags and set them afresh to the list provided. The + default action is adding. + +

Example usage:

+ +

+        # same as 'tags 123456 + patch'
+        tags 123456 patch
+
+        # same as 'tags 123456 + help security'
+        tags 123456 help security
+
+        # add 'fixed' and 'pending' tags
+        tags 123456 + fixed pending
 
-  Sets a particular tag for the $gBug report #bugnumber to
-  tag. No notification is sent to the user who reported the $gBug.
-  + means adding, - means subtracting, and
-  = means ignoring the current tags and setting them afresh.
-  The default action is adding.
+        # remove 'unreproducible' tag
+        tags 123456 - unreproducible
+
+        # set tags to exactly 'moreinfo' and 'unreproducible'
+        tags 123456 = moreinfo unreproducible
+

Available tags currently include patch, wontfix, moreinfo, unreproducible, help, @@ -198,7 +270,24 @@ mailservers is available via the WWW, in

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

close bugnumber +

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)

Close $gBug report #bugnumber. @@ -210,19 +299,22 @@ mailservers is available via the WWW, in who reported the $gBug knows why it is being closed. The use of this command is therefore deprecated. +

If you supply a fixed-version, the $gBug tracking system + will note that the $gBug was fixed in that version of the package. +

package [ packagename ... ]

Limits the following commands so that they will only apply to bugs filed against the listed packages. You can list one or more packages. If you don't list any packages, the following commands will apply to all bugs. You're encouraged to use this as a safety feature in case you - accidentally use the wrong bug numbers.

Example usage:

         package foo
-        reassign 123456 bar
+        reassign 123456 bar 1.0-1
 
         package bar
         retitle 123456 bar: bar sucks
@@ -232,18 +324,56 @@ mailservers is available via the WWW, in
         severity 234567 wishlist

quit -

stop -

thank... -

--... +

owner bugnumber address | ! -

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. +

Sets address to be the "owner" of #bugnumber. + 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 + ! shorthand or specify your own email address.

+ +

noowner bugnumber + +

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. + The text of comments will be included in the acknowledgement sent to the + sender and to affected maintainers, so you can use this to document the + reasons for your commands. + +

quit +

stop +

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.