add rebuild-debinfo

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

diff --git a/html/server-control.html.in b/html/server-control.html.in
index ebed2ca368f1095934f70288c4736e9e404683d8..3c61089e866622e78be3decec8905fd90d3b91a5 100644 (file)
--- a/html/server-control.html.in
+++ b/html/server-control.html.in
@@ -325,8 +325,8 @@ mailservers is available via the WWW, in
 <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
@@ -337,6 +337,18 @@ mailservers is available via the WWW, in
   <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.