* Fix the documentation of clone to indicate that you need at least

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

diff --git a/html/server-control.html.in b/html/server-control.html.in
index 579cf8bcd3815d7cbad3272e8f126a3d292f4b74..e570f4a997117893cb0c2c6df82c355ffbbf0c2d 100644 (file)
--- a/html/server-control.html.in
+++ b/html/server-control.html.in
@@ -150,7 +150,7 @@ mailservers is available via the WWW, in
   <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
@@ -202,6 +202,12 @@ mailservers is available via the WWW, in
   <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