X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=html%2Fserver-control.html.in;h=95649cc54d886a20cc9325494d436943f1251f19;hb=975055914729daa5d622a6abe072be35a008b11e;hp=69fb0661964d290c24e745d5c6e416aa5dafe1bd;hpb=92f20f5069013354e5e42d498e1332cd2a44b554;p=debbugs.git
diff --git a/html/server-control.html.in b/html/server-control.html.in
index 69fb066..95649cc 100644
--- a/html/server-control.html.in
+++ b/html/server-control.html.in
@@ -3,7 +3,9 @@ $gControlHtml = <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.
close
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
+ [ version ]
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 | =
| !
]
@@ -75,10 +70,61 @@ mailservers is available via the WWW, in
again.
If the $gBug is not closed then reopen won't do anything, not even
- change the originator. There is no way to change the originator of an
- open $gBug report (this is deliberate, so that you can't have a $gBug be
- closed and then deleted $gRemoveAge days later without someone being told about
- it).
+ change the originator. To change the originator of an open $gBug report,
+ 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 ]
+
+ 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
+
+ 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 | !
+
+ If you wish to become the new originator of the report you can use
+ the !
shorthand or specify your own email address.
While the reopen
command changes the originator of other
+ bugs merged with the one being reopened, submitter
does not
+ affect merged bugs.
forwarded
bugnumber address
@@ -97,7 +143,7 @@ mailservers is available via the WWW, in
retitle
bugnumber new-title
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 +158,30 @@ mailservers is available via the WWW, in
For their meanings please consult the general developers' documentation for the $gBug system. +
clone
bugnumber NewID [ new IDs ... ]
+
+ 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 -3 + reassign -3 foo + retitle -3 foo: foo sucks + merge -1 -3 ++
merge
bugnumber bugnumber ...
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
. 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
@@ -134,11 +205,17 @@ 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. +
forcemerge
bugnumber bugnumber ...
+ unmerge
bugnumber
unmerge
commands in your message.
+tags
bugnumber [ +
| -
| =
] tag [ tag ... ]
+
+ +
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 + + # 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
,
+ pending
, fixed
, security
,
+ upstream
, potato
, woody
,
+ sarge
,
+ sid
and experimental
.
+
+
For their meanings please consult the + general developers' documentation for the $gBug system. + +
block
|unblock
bugnumber by
|with
bug [ bug ... ]
+
+ 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)
+
+ 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.
+
+
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 ... ]
+
+ Example usage:
+ ++ package foo + reassign 123456 bar 1.0-1 + + package bar + retitle 123456 bar: bar sucks + severity 123456 normal + + package + severity 234567 wishlist ++ +
owner
bugnumber address | !
+
+ If you wish to become the owner of the $gBug yourself, you can use the
+ !
shorthand or specify your own email address.
noowner
bugnumber
+
+ archive
bugnumber
+
+ unarchive
bugnumber
+
+ #
...
+
+ #
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
+--
+
+
+
+
+