Mail servers' reference card

   Full documentation of the mail servers is available on the WWW, in the
   files bug-log-mailserver.txt and bug-maint-mailcontrol.txt or by
   sending the word help to each mailserver.

Synopsis of commands available at request

     * send bugnumber
     * send-detail bugnumber
     * index [full]
     * index-summary by-package
     * index-summary by-number
     * index-maint
     * index maint maintainer
     * index-packages
     * index packages package
     * send-unmatched [this|0]
     * send-unmatched last|-1
     * send-unmatched old|-2
     * getinfo filename (see below)
     * help
     * refcard
     * user email
     * usertag bugnumber [+-=] tag ...
     * quit|stop|thank...|--...
     * #... (comment)
     * debug level

  List of info files for getinfo

     * maintainers
     * override.stable
     * override.development
     * override.contrib
     * override.non-free
     * override.experimental
     * override.codeword
     * pseudo-packages.description
     * pseudo-packages.maintainers

Synopsis of extra commands available at control mailserver

     * close bugnumber [ fixed-version ] (you must separately tell
       originator why)
     * reassign bugnumber package [ version ]
     * severity bugnumber severity
     * reopen bugnumber [ originator-address | = | ! ]
     * found bugnumber [ version ]
     * notfound bugnumber version
     * submitter bugnumber originator-address | !
     * forwarded bugnumber address
     * notforwarded bugnumber
     * owner bugnumber address | !
     * noowner bugnumber
     * retitle bugnumber new-title
     * clone bugnumber NewID [ new IDs ... ]
     * merge bugnumber bugnumber ...
     * forcemerge bugnumber bugnumber ...
     * unmerge bugnumber
     * tag bugnumber [+-=] tag ...
     * block bugnumber by bug ...
     * unblock bugnumber by bug ...

   reopen with = or no originator address leaves the originator as the
   original submitter; ! sets it to you, the person doing the reopen.

   critical
          makes unrelated software on the system (or the whole system)
          break, or causes serious data loss, or introduces a security
          hole on systems where you install the package.

   grave
          makes the package in question unusable or mostly so, or causes
          data loss, or introduces a security hole allowing access to the
          accounts of users who use the package.

   normal
          the default value, for normal Bugs.

   wishlist
          for any feature request, and also for any Bugs that are very
          difficult to fix due to major design considerations.

Synopsis of bug submission and followup addresses

     * nnn[ -submit | ]
     * nnn-maintonly
     * nnn-quiet
     * nnn-forwarded
     * nnn-request
     * nnn-submitter
     * nnn-done
     * nnn-close
     * nnn-subscribe
     __________________________________________________________________

   Other pages:
     * Bug tracking system main contents page.
     * Full documentation of the request mailserver.
     * Full documentation of the control mailserver.
     * Instructions for reporting Bugs.
     * Accessing the Bug tracking logs other than by WWW.
     * Developers' information regarding the Bug processing system.
     * Full list of outstanding and recent Bug reports.
     * Packages with Bug reports.
     * Maintainers of packages with Bug reports.


    X2Go Developers <owner@bugs.x2go.org>. Last modified: Wed, 5 May 2021
    08:01:35 UTC
    For more information on viewing bug history, submitting new reports,
    modifying existing ones and general BTS usage please visit
    http://wiki.x2go.org/doku.php/wiki:bugs (FAQ).
    X2Go Bug Tracking System (based on the software used for Debian's
    BTS)
    Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation
    Ltd, 1994-97 Ian Jackson.