[project @ 2004-05-11 00:51:01 by cjwatson]

[debbugs.git] / html / server-control.html.in

diff --git a/html/server-control.html.in b/html/server-control.html.in
index b943f0238b6deaaa8378f598234c85663df91b70..f5e96660ab43c02a1a254880854338606ff7babf 100644 (file)
--- a/html/server-control.html.in
+++ b/html/server-control.html.in
@@ -210,6 +210,50 @@ 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.
 
+<dt><code>package</code> [ <var>packagename</var> ... ]
+
+  <dd>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.
+
+  <p>Example usage:</p>
+
+  <pre>
+        package foo
+        reassign 123456 bar
+
+        package bar
+        retitle 123456 bar: bar sucks
+        severity 123456 normal
+
+        package
+        severity 234567 wishlist
+  </pre>
+
+<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
+  package has a team of maintainers.
+
+  <p>If you wish to become the owner of the $gBug yourself, you can use the
+  <code>!</code> shorthand or specify your own email address.</p>
+
+<dt><code>noowner</code> <var>bugnumber</var>
+
+  <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>#</code>...
+
+  <dd>One-line comment. The <code>#</code> 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.
+
 <dt><code>quit</code>
 <dt><code>stop</code>
 <dt><code>thank</code>...
@@ -219,10 +263,6 @@ mailservers is available via the WWW, in
       of the message can include explanations, signatures or anything else,
       none of it will be detected by the control server.
 
-<dt><code>#</code>...
-
-  <dd>One-line comment. The <code>#</code> must be at the start of the line.
-
 </dl>
 
 <hr>