<head>
<title>$gProject $gBug system - control mail server commands</title>
<link rev="made" href="mailto:$gMaintainerEmail">
+ <link rel="stylesheet" href="$gWebHostBugDir/css/bugs.css" type="text/css">
</head>
<body>
the $gBug is cleared. This is identical to the behaviour of
<code>reopen</code>.
+ <p>This command will only cause a bug to be marked as not done if no
+ version is specified, or if the <var>version</var> being marked found
+ is equal to the <var>version</var> which was last marked fixed. (If
+ you are certain that you want the bug marked as not done,
+ use <code>reopen</code> in conjunction with <code>found</code>.</p>
+
<p>This command was introduced in preference to <code>reopen</code>
because it was difficult to add a <var>version</var> to that command's
syntax without suffering ambiguity.
<p>For <a href="Developer.html#severities">their meanings</a> please
consult the general developers' documentation for the $gBug system.
-<dt><code>clone</code> <var>bugnumber</var> [ <var>new IDs</var> ]
+<dt><code>clone</code> <var>bugnumber</var> <var>NewID</var> [ <var>new IDs</var> ... ]
<dd>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
<p>Merged reports are all expired simultaneously, and only when all of
the reports each separately meet the criteria for expiry.
+<dt><code>forcemerge</code> <var>bugnumber</var> <var>bugnumber</var> ...
+ <dd>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.
+
<dt><code>unmerge</code> <var>bugnumber</var>
<dd>Disconnects a $gBug report from any other reports with which it may have
<dt><code>owner</code> <var>bugnumber</var> <var>address</var> | <code>!</code>
<dd>Sets <var>address</var> to be the "owner" of #<var>bugnumber</var>.
- 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.
<p>If you wish to become the owner of the $gBug yourself, you can use the
<dd>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.
+<dt><code>archive</code> <var>bugnumber</var>
+
+ <dd>Archives a $gBug that was previously archived if the $gBug
+ fulfills the requirements for archival, ignoring time.
+
+<dt><code>unarchive</code> <var>bugnumber</var>
+
+ <dd>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.
+
<dt><code>#</code>...
<dd>One-line comment. The <code>#</code> must be at the start of the line.
<dt><code>quit</code>
<dt><code>stop</code>
-<dt><code>thank</code>...
-<dt><code>--</code>...
-
- <dd>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.
+<dt><code>thank</code>
+<dt><code>thanks</code>
+<dt><code>thankyou</code>
+<dt><code>thank you</code>
+<dt><code>--</code>
+<!-- #366093, I blame you! -->
+<!-- <dt><code>kthxbye</code> -->
+<!-- See... I documented it! -->
+
+ <dd>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.
</dl>
projects / debbugs.git / blobdiff