+ <p>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
+ <code>found</code> command instead.
+
+<dt><code>found</code> <var>bugnumber</var> [ <var>version</var> ]
+
+ <dd>Record that #<var>bugnumber</var> has been encountered in the given
+ <var>version</var> of the package to which it is assigned.
+
+ <p>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.
+
+ <p>If no <var>version</var> is given, then the list of fixed versions for
+ 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.
+
+<dt><code>notfound</code> <var>bugnumber</var> <var>version</var>
+
+ <dd>Remove the record that #<var>bugnumber</var> was encountered in the
+ given <var>version</var> of the package to which it is assigned.
+
+ <p>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.
+