Commits

Anonymous committed ca06083

Update to package standard 1.0

  • Participants
  • Parent commits f8f481f

Comments (0)

Files changed (9)

+1998-01-24  SL Baur  <steve@altair.xemacs.org>
+
+	* Makefile (VERSION): Update to package standard 1.0.
+
 1998-01-12  SL Baur  <steve@altair.xemacs.org>
 
 	* Makefile: Update to newer package interface.
 # the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
 # Boston, MA 02111-1307, USA.
 
-VERSION = 1.01
+VERSION = 1.02
+AUTHOR_VERSION = 3.101
+MAINTAINER = XEmacs Development Team <xemacs-beta@xemacs.org>
 PACKAGE = gnats
 PKG_TYPE = regular
 REQUIRES = mail-lib xemacs-base
 	rm -f $(ELCS) auto-autoloads.elc texi/*.info*
 
 texi:
-	$(MAKE) -C texi $(MAKEFLAGS)
+	$(MAKE) -C texi $(MFLAGS)
 
 srckit: srckit-std
 
 	mkdir -p $(STAGING)/lisp/$(PACKAGE)
 	mkdir -p $(STAGING)/etc/$(PACKAGE)
 	mkdir -p $(STAGING)/info
-	cp -a ChangeLog *.el* $(STAGING)/lisp/$(PACKAGE)
-	cp -a texi/gnats.info* $(STAGING)/info
-	cp -a texi/send-pr.info* $(STAGING)/info
-	cp -a etc/categories $(STAGING)/etc
-	cp -a etc/xemacs.org $(STAGING)/etc/$(PACKAGE)
+	$(RCOPY) ChangeLog *.el* $(STAGING)/lisp/$(PACKAGE)
+	$(RCOPY) texi/gnats.info* $(STAGING)/info
+	$(RCOPY) texi/send-pr.info* $(STAGING)/info
+	$(RCOPY) etc/categories $(STAGING)/etc
+	$(RCOPY) etc/xemacs.org $(STAGING)/etc/$(PACKAGE)
 	(cd $(STAGING); \
 	rm -f $(PACKAGE)-$(VERSION)-pkg.tar*; \
 	tar cf $(PACKAGE)-$(VERSION)-pkg.tar lisp/$(PACKAGE) \
 (gnats
-  (version VERSION
+  (standards-version 1.0
+   version VERSION
+   author-version AUTHOR_VERSION
+   date DATE
+   build-date BUILD_DATE
+   maintainer MAINTAINER
+   distribution stable
+   priority high
+   category CATEGORY
+   dump nil
    description "XEmacs bug reports."
    filename FILENAME
    md5sum MD5SUM

texi/gnats.info

-This is Info file gnats.info, produced by Makeinfo version 1.68 from
-the input file gnats.texi.
-
-START-INFO-DIR-ENTRY
-* Keeping Track: (gnats).        GNU Problem Report Management System
-END-INFO-DIR-ENTRY
-
-   Copyright (C) 1993, 1995 Free Software Foundation, Inc.
-
-   Permission is granted to make and distribute verbatim copies of this
-manual provided the copyright notice and this permission notice are
-preserved on all copies.
-
-   Permission is granted to copy and distribute modified versions of
-this manual under the conditions for verbatim copying, provided also
-that the entire resulting derived work is distributed under the terms
-of a permission notice identical to this one.
-
-   Permission is granted to copy and distribute translations of this
-manual into another language, under the above conditions for modified
-versions.
-
-
-Indirect:
-gnats.info-1: 839
-gnats.info-2: 47352
-gnats.info-3: 96127
-gnats.info-4: 143682
-
-Tag Table:
-(Indirect)
-Node: Top839
-Node: Introduction2463
-Node: Paradigm3607
-Node: Flowchart8195
-Node: States10301
-Node: Fields11744
-Node: Mail header fields15351
-Node: Problem Report fields16434
-Node: Invoking the tools24401
-Node: send-pr27357
-Node: using send-pr28288
-Node: send-pr in Emacs34671
-Node: send-pr from the shell39020
-Node: Helpful hints41535
-Node: edit-pr44633
-Node: edit-pr in Emacs47352
-Node: edit-pr from the shell52121
-Node: query-pr53221
-Node: Invoking query-pr54165
-Node: Example queries63394
-Node: Reporting64627
-Node: view-pr67197
-Node: Management67784
-Node: Networked management72297
-Node: Local configuration73723
-Node: default behavior76603
-Node: config77979
-Node: categories84762
-Node: responsible88151
-Node: submitters89332
-Node: Admin files92454
-Node: index file92881
-Node: current file93860
-Node: Admin utils94115
-Node: mkcat94616
-Node: rmcat96127
-Node: gen-index97998
-Node: mkdist99231
-Node: Internal utils100625
-Node: queue-pr101152
-Node: file-pr102938
-Node: at-pr105116
-Node: pr-edit106438
-Node: pr-addr109480
-Node: Installation109886
-Node: Configure and make112120
-Node: Installing utils116583
-Node: Aliases120143
-Node: Installing the daemon123293
-Node: Installing tools124745
-Node: Upgrading128626
-Node: Locations130118
-Node: prefix130531
-Node: exec-prefix131176
-Node: GNATS_ROOT133428
-Node: defaults134089
-Node: Regexps138348
-Node: Index143682
-
-End Tag Table

texi/gnats.info-1

-This is Info file gnats.info, produced by Makeinfo version 1.68 from
-the input file gnats.texi.
-
-START-INFO-DIR-ENTRY
-* Keeping Track: (gnats).        GNU Problem Report Management System
-END-INFO-DIR-ENTRY
-
-   Copyright (C) 1993, 1995 Free Software Foundation, Inc.
-
-   Permission is granted to make and distribute verbatim copies of this
-manual provided the copyright notice and this permission notice are
-preserved on all copies.
-
-   Permission is granted to copy and distribute modified versions of
-this manual under the conditions for verbatim copying, provided also
-that the entire resulting derived work is distributed under the terms
-of a permission notice identical to this one.
-
-   Permission is granted to copy and distribute translations of this
-manual into another language, under the above conditions for modified
-versions.
-
-
-File: gnats.info,  Node: Top,  Next: Introduction,  Up: (dir)
-
-Overview
-********
-
-   This manual documents GNATS, the GNU Problem Report Management
-System, version 3.101.  GNATS is a bug-tracking tool designed for use
-at a central "Support Site".  Users who experience problems use
-electronic mail to communicate these problems to "maintainers" at that
-Support Site.  GNATS partially automates the tracking of these "Problem
-Reports" ("PR"s) by:
-
-   * organizing problem reports into a database and notifying
-     responsible parties of suspected bugs;
-
-   * allowing support personnel and their managers to edit and query
-     accumulated bugs; and
-
-   * providing a reliable archive of problems (and their subsequent
-     solutions) with a given program.
-
-   GNATS offers many of the same features offered by more generalized
-databases, including editing, querying, and basic reporting.  The GNATS
-database itself is an ordered repository for problem reports; each PR
-receives a unique, incremental "PR number" which identifies it
-throughout its lifetime.  For a discussion on the working system
-adopted by GNATS, see *Note The database paradigm: Paradigm.
-
-   You can access the submitting, editing, and querying functions of
-GNATS from within GNU Emacs.  *Note Invoking the GNATS tools: Invoking
-the tools.
-
-* Menu:
-
-* Introduction::          Introducing GNATS
-* Invoking the tools::    Invoking the GNATS tools
-* Management::            GNATS Administration
-* Installation::          Installing GNATS
-* Locations::             Where GNATS lives
-* Regexps::               Querying using regular expressions
-* Index::
-
-
-File: gnats.info,  Node: Introduction,  Next: Invoking the tools,  Prev: Top,  Up: Top
-
-Introducing GNATS
-*****************
-
-   Any support organization realizes that a large amount of data flows
-back and forth between the maintainers and the users of their products.
-This data often takes the form of problem reports and communication via
-electronic mail.  GNATS addresses the problem of organizing this
-communication by defining a database made up of archived and indexed
-electronic mail messages.
-
-   GNATS was designed as a tool for software maintainers.  It consists
-of several utilities which, when used in concert, formulate and
-administer a database of Problem Reports grouped by site-defined
-"problem categories".  It allows a support organization to keep track
-of problems (hence the term "Problem Report") in an organized fashion.
-Essentially, GNATS acts as an active archive for field-separated
-textual data submitted through electronic mail.
-
-* Menu:
-
-* Paradigm::       The database paradigm
-* Flowchart::      Flowchart of GNATS activities
-* States::         States of Problem Reports
-* Fields::         Problem Report format
-
-
-File: gnats.info,  Node: Paradigm,  Next: Flowchart,  Up: Introduction
-
-The database paradigm
-=====================
-
-   It is in your best interest as the maintainer of a body of work to
-organize the feedback you receive on that work, and to make it easy for
-users of your work to report problems and suggestions.
-
-   GNATS makes this easy by automatically filing incoming problem
-reports into appropriate places, by notifying responsible parties of the
-existence of the problem and (optionally) sending an acknowledgement to
-the submitter that the report was received, and by making these Problem
-Reports accessible to queries and easily editable.  GNATS is a database
-specialized for a specific task.
-
-   GNATS was designed for use at a Support Site that handles a high
-level of problem-related traffic though electronic mail.  It maintains
-Problem Reports in the form of text files with defined "fields" (*note
-GNATS data fields: Fields.).  The location of the database, as well as
-the categories it accepts as valid, the maintainers for whom it
-provides service, and the submitters from whom it accepts Problem
-Reports, are all definable by the "Support Site".  *Note GNATS
-administration: Management.
-
-   Each PR is a separate file within a main repository (*note Where
-GNATS lives: Locations.).  Editing access to the database is regulated
-to maintain consistency, but anyone with electronic mail access may
-submit Problem Reports.  To make queries on the database faster, an
-index is kept automatically (*note The `index' file: index file.).
-
-   We provide several software tools so that users may submit new
-Problem Reports, edit existing Problem Reports, and query the database.
-
-   * `send-pr' is used by both product maintainers and the end users of
-     the products they support to submit PRs to the database.
-
-   * `edit-pr' is used by maintainers to use when editing problem
-     reports in the database.
-
-   * Maintainers, managers and administrators can use `query-pr' to
-     make inquiries about indidvidual PRs or groups of PRs.
-
-   `send-pr' can also be packaged by itself and distributed to anyone
-you wish to receive Problem  Reports  from; see *Note Configuring
-`send-pr' for the outside world: mkdist.
-
-   At the Support Site, a GNATS "administrator" is charged with the
-duty of maintaining GNATS.  These duties are discussed in detail in
-*Note GNATS Administration: Management, and generally include
-configuring GNATS for the Support Site, editing PRs that GNATS cannot
-process, pruning log files, setting up new problem categories, backing
-up the database, and distributing `send-pr' so that others may submit
-Problem Reports.
-
-   Responsibility for a given Problem Report depends on the category of
-the problem.  Optionally, an automated reminder can be sent to the
-responsible person if a problem report is neglected for a requisite time
-period.  *Note Changing your local configuration: Local configuration.
-
-   GNATS does not have the ability to decipher random text, so any
-problem reports which arrive in a format GNATS does not recognize are
-placed in a separate directory pending investigation by the GNATS
-administrator (*note GNATS Administration: Management.).
-
-   Once a problem is recorded in the database, work can begin toward a
-solution.  A problem's initial "state" is `open' (*note States of
-Problem Reports: States.).  An acknowledgement is sent to the
-originator of the bug report (if that feature of GNATS is activated).
-GNATS forwards copies of the report to the party responsible for that
-problem category and to the person responsible for problems arriving
-from that "Submitter Site".
-
-   When a problem has been identified, the maintainer can change its
-state to `analyzed', and then to `feedback' when a solution is found.
-Each time the state of a PR changes, the submitter of the problem
-report is notified of the reason for the change.  If the party
-responsible for the PR changes, the previous responsible party and the
-new responsible party receive notice of the change.  The change and
-reason are also recorded in the `>Audit-Trail:' field of the Problem
-Report.  (*Note Editing existing Problem Reports: edit-pr.  For
-information on the `>Audit-Trail:' field, see *Note Problem Report
-format: Fields.)
-
-   When the originator of the Problem Report confirms that the solution
-works, the maintainer can change the state to "closed".  If the PR
-cannot be closed, the maintainer can change its state to "suspended" as
-a last resort.  (For a more detailed description of these states, see
-*Note States of Problem Reports: States.)
-
-
-File: gnats.info,  Node: Flowchart,  Next: States,  Prev: Paradigm,  Up: Introduction
-
-Flowchart of GNATS activities
-=============================
-
-   This informal flowchart shows the relationships of the GNATS tools
-to each other and to the files with which they interoperate.
-
-     +===========+    +===========+    +===========+
-     # USER SITE #    # USER SITE #    # USER SITE #
-     #           #    #           #    #           #
-     # *send-pr* #    # *send-pr* #    # *send-pr* #
-     +=====|=====+    +=====|=====+    +=====|=====+
-           |                V                |
-           `--------->    Email....  <-------'
-                     ,--->     |
-     +===============|=========|===================+
-     # SUPPORT SITE  |         `---> /etc/aliases  #
-     #          *send-pr*                |         #
-     #     +-----------------------------V--------+#
-     #     | GNATS         GNATS_ROOT/gnats-queue/|#
-     #     |                             |        |#
-     #     |        _________            V        |#
-     #     |       |*file-pr*|<--- *queue-pr -r*  |#
-     #     |       |         |                    |#
-     #  _  |       |  valid  |                    |#
-     # |M| |       |Category?|N--.                |#
-     # |A| |       |_________|   |      GNATS     |#
-     # |I| |              Y|     |  ADMINISTRATOR |#
-     # |N| |               |     |                |#
-     # |T|<----------------|     |                |#
-     # |A| |               |     |  .-> *edit-pr* |#
-     # |I|--->*edit-pr*-.  |     V  |           | |#
-     # |N| |            |  |GNATS_ROOT/pending  | |#
-     # |E|<--*query-pr* |  |                    | |#
-     # |R| |       |    |  |                    | |#
-     # |S| |       |    V  V                    V |#
-     # |_| |+------------------------------------+|#
-     #     ||         GNATS Database             ||#
-     #     ||   GNATS_ROOT/CATEGORY/GNATS-ID     ||#
-     #     |+------------------------------------+|#
-     #     +--------------------------------------+#
-     +=============================================+
-
-
-File: gnats.info,  Node: States,  Next: Fields,  Prev: Flowchart,  Up: Introduction
-
-States of Problem Reports
-=========================
-
-   Each PR goes through a defined series of states between origination
-and closure.  The originator of a PR receives notification
-automatically of any state changes.
-
-"open"
-     The initial state of a Problem Report.  This means the PR has been
-     filed and the responsible person(s) notified.
-
-"analyzed"
-     The responsible person has analyzed the problem.  The analysis
-     should contain a preliminary evaluation of the problem and an
-     estimate of the amount of time and resources necessary to solve
-     the problem.  It should also suggest possible workarounds.
-
-"feedback"
-     The problem has been solved, and the originator has been given a
-     patch or other fix.  The PR remains in this state until the
-     originator acknowledges that the solution works.
-
-"closed"
-     A Problem Report is closed ("the bug stops here") only when any
-     changes have been integrated, documented, and tested, and the
-     submitter has confirmed the solution.
-
-"suspended"
-     Work on the problem has been postponed.  This happens if a timely
-     solution is not possible or is not cost-effective at the present
-     time.  The PR continues to exist, though a solution is not being
-     actively sought.  If the problem cannot be solved at all, it
-     should be closed rather than suspended.
-
-
-File: gnats.info,  Node: Fields,  Prev: States,  Up: Introduction
-
-Problem Report format
-=====================
-
-   The format of a PR is designed to reflect the nature of GNATS as a
-database.  Information is arranged into "fields", and kept in
-individual records (Problem Reports).
-
-   Problem Report fields are denoted by a keyword which begins with `>'
-and ends with `:', as in `>Confidential:'.  Fields belong to one of
-three data types:
-
-ENUMERATED
-     One of a specific set of values, which vary according to the
-     field.  The value for each keyword must be on the same line as the
-     keyword.  These values are not configurable (yet).
-
-     The following fields are ENUMERATED format; see the descriptions of
-     fields below for explanations of each field in detail:
-
-          >Confidential:   >Severity:       >Priority:
-          >Class:          >State:          >Number:
-
-TEXT
-     One single line of text which must begin and end on the same line
-     (i.e., before a newline) as the keyword.  See the descriptions of
-     fields below for explanations of each field in detail.  The
-     following fields are TEXT format:
-
-          >Submitter-Id:   >Originator:     >Synopsis:
-          >Category:       >Release:        >Responsible:
-          >Arrival-Date:
-
-MULTITEXT
-     Text of any length may occur in this field.  MULTITEXT may span
-     multiple lines and may also include blank lines.  A MULTITEXT field
-     ends only when another keyword appears.  See the descriptions of
-     fields below for explanations of each field in detail.
-
-     The following fields are MULTITEXT format:
-
-          >Organization:   >Environment:    >Description:
-          >How-To-Repeat:  >Fix:            >Audit-Trail:
-          >Unformatted:
-
-   A Problem Report contains two different types of fields: "Mail
-Header" fields, which are used by the mail handler for delivery, and
-"Problem Report" fields, which contain information relevant to the
-Problem Report and its submitter.  A Problem Report is essentially a
-specially formatted electronic mail message.
-
-Example Problem Report
-----------------------
-
-   The following is an example Problem Report.  Mail headers are at the
-top, followed by GNATS fields, which begin with `>' and end with `:'.
-The `Subject:' line in the mail header and the `>Synopsis:' field are
-usually duplicates of each other.
-
-     Message-Id:  MESSAGE-ID
-     Date:        DATE
-     From:        ADDRESS
-     Reply-To:    ADDRESS
-     To:          BUG-ADDRESS
-     Subject:     SUBJECT
-     
-     >Number:       GNATS-ID
-     >Category:     CATEGORY
-     >Synopsis:     SYNOPSIS
-     >Confidential: yes *or* no
-     >Severity:     critical, serious, *or* non-critical
-     >Priority:     high, medium *or* low
-     >Responsible:  RESPONSIBLE
-     >State:        open, analyzed, suspended, feedback, *or* closed
-     >Class:        sw-bug, doc-bug, change-request, support,
-     duplicate, *or* mistaken
-     >Submitter-Id: SUBMITTER-ID
-     >Arrival-Date: DATE
-     >Originator:   NAME
-     >Organization: ORGANIZATION
-     >Release:      RELEASE
-     >Environment:
-        ENVIRONMENT
-     >Description:
-        DESCRIPTION
-     >How-To-Repeat:
-        HOW-TO-REPEAT
-     >Fix:
-        FIX
-     >Audit-Trail:
-     APPENDED-MESSAGES...
-     State-Changed-From-To: FROM-TO
-     State-Changed-When: DATE
-     State-Changed-Why:
-        REASON
-     Responsible-Changed-From-To: FROM-TO
-     Responsible-Changed-When: DATE
-     Responsible-Changed-Why:
-        REASON
-     >Unformatted:
-        MISCELLANEOUS
-
-* Menu:
-
-* Mail header fields::
-* Problem Report fields::
-
-
-File: gnats.info,  Node: Mail header fields,  Next: Problem Report fields,  Up: Fields
-
-Mail header fields
-------------------
-
-   A Problem Report may contain any mail header field described in the
-Internet standard RFC-822.  However, only the fields which identify the
-sender and the subject are required by `send-pr':
-
-`To:'
-     The preconfigured mail address for the Support Site where the PR
-     is to be sent, automatically supplied by `send-pr'.
-
-`Subject:'
-     A terse description of the problem.  This field normally contains
-     the same information as the `>Synopsis:' field.
-
-`From:'
-     Usually supplied automatically by the originator's mailer; should
-     contain the originator's electronic mail address.
-
-`Reply-To:'
-     A return address to which electronic replies can be sent; in most
-     cases, the same address as the `From:' field.
-
-   One of the configurable options for GNATS is whether or not to
-retain `Received-By:' headers, which often consume a lot of space and
-are not often used.  *Note Changing your local configuration: Local
-configuration.
-
-
-File: gnats.info,  Node: Problem Report fields,  Prev: Mail header fields,  Up: Fields
-
-Problem Report fields
----------------------
-
-Field descriptions
-------------------
-
-   The following fields are present whenever a PR is submitted via the
-program `send-pr'.  GNATS adds additional fields when the PR arrives at
-the Support Site; explanations of these follow this list.
-
-`>Submitter-Id:'
-     (TEXT) A unique identification code assigned by the Support Site.
-     It is used to identify all Problem Reports coming from a particular
-     site.  (Submitters without a value for this field can invoke
-     `send-pr' with the `--request-id' option to apply for one from the
-     support organization.  Problem Reports from those not affiliated
-     with the support organization should use the default value of `net'
-     for this field.)
-
-`>Originator:'
-     (TEXT) Originator's real name.  The default is the value of the
-     originator's environment variable `NAME'.
-
-`>Organization:'
-     (MULTITEXT) The originator's organization.  The default value is
-     set with the variable `DEFAULT_ORGANIZATION' in the `config' file
-     (*note The `config' file: config.).
-
-`>Confidential:'
-     (ENUMERATED) Use of this field depends on the originator's
-     relationship with the support organization; contractual agreements
-     often have provisions for preserving confidentiality.  Conversely,
-     a lack of a contract often means that any data provided will not
-     be considered confidential.  Submitters should be advised to
-     contact the support organization directly if this is an issue.
-
-     If the originator's relationship to the support organization
-     provides for confidentiality, then if the value of this field is
-     `yes' the support organization treats the PR as confidential; any
-     code samples provided are not made publicly available (e.g., in
-     regression test suites).  The default value is `yes'.
-
-`>Synopsis:'
-     (TEXT) One-line summary of the problem.  `send-pr' copies this
-     information to the `Subject:' line when you submit a Problem
-     Report.
-
-`>Severity:'
-     (ENUMERATED) The severity of the problem.  Accepted values include:
-
-    `critical'
-          The product, component or concept is completely
-          non-operational or some essential functionality is missing.
-          No workaround is known.
-
-    `serious'
-          The product, component or concept is not working properly or
-          significant functionality is missing.  Problems that would
-          otherwise be considered `critical' are rated `serious' when a
-          workaround is known.
-
-    `non-critical'
-          The product, component or concept is working in general, but
-          lacks features, has irritating behavior, does something
-          wrong, or doesn't match its documentation.
-
-     The default value is `serious'.
-
-`>Priority:'
-     (ENUMERATED) How soon the originator requires a solution.  Accepted
-     values include:
-
-    `high'
-          A solution is needed as soon as possible.
-
-    `medium'
-          The problem should be solved in the next release.
-
-    `low'
-          The problem should be solved in a future release.
-
-     The default value is `medium'.
-
-`>Category:'
-     (TEXT) The name of the product, component or concept where the
-     problem lies.  The values for this field are defined by the Support
-     Site.  *Note The `categories' file: categories, for details.
-
-`>Class:'
-     (ENUMERATED) The class of a problem can be one of the following:
-
-    `sw-bug'
-          A general product problem.  (`sw' stands for "software".)
-
-    `doc-bug'
-          A problem with the documentation.
-
-    `change-request'
-          A request for a change in behavior, etc.
-
-    `support'
-          A support problem or question.
-
-    `duplicate (PR-NUMBER)'
-          Duplicate PR.  PR-NUMBER should be the number of the original
-          PR.
-
-    `mistaken'
-          No problem, user error or misunderstanding.  This value is
-          valid only at the Support Site.
-
-     The default is `sw-bug'.
-
-`>Release:'
-     (TEXT) Release or version number of the product, component or
-     concept.
-
-`>Environment:'
-     (MULTITEXT) Description of the environment where the problem
-     occured: machine architecture, operating system, host and target
-     types, libraries, pathnames, etc.
-
-`>Description:'
-     (MULTITEXT) Precise description of the problem.
-
-`>How-To-Repeat:'
-     (MULTITEXT) Example code, input, or activities to reproduce the
-     problem.  The support organization uses example code both to
-     reproduce the problem and to test whether the problem is fixed.
-     Include all preconditions, inputs, outputs, conditions after the
-     problem, and symptoms.  Any additional important information
-     should be included.  Include all the details that would be
-     necessary for someone else to recreate the problem reported,
-     however obvious.  Sometimes seemingly arbitrary or obvious
-     information can point the way toward a solution.  See also *Note
-     Helpful hints: Helpful hints.
-
-`>Fix:'
-     (MULTITEXT) A description of a solution to the problem, or a patch
-     which solves the problem.  (This field is most often filled in at
-     the Support Site; we provide it to the submitter in case she has
-     solved the problem.)
-
-GNATS adds the following fields when the PR arrives at the Support Site:
-
-`>Number:'
-     (ENUMERATED) The incremental identification number for this PR.
-     This is included in the automated reply to the submitter (if that
-     feature of GNATS is activated; *note Changing your local
-     configuration: Local configuration.).  It is also included in the
-     copy of the PR that is sent to the maintainer.
-
-     The `>Number:' field is often paired with the `>Category:' field as
-
-          CATEGORY/NUMBER
-
-     in subsequent email messages.  This is for historical reasons, as
-     well as because Problem Reports are stored in subdirectories which
-     are named by category.
-
-`>State:'
-     (ENUMERATED) The current state of the PR.  Accepted values are:
-
-    `open'
-          The PR has been filed and the responsible person notified.
-
-    `analyzed'
-          The responsible person has analyzed the problem.
-
-    `feedback'
-          The problem has been solved, and the originator has been
-          given a patch or other fix.
-
-    `closed'
-          The changes have been integrated, documented, and tested, and
-          the originator has confirmed that the solution works.
-
-    `suspended'
-          Work on the problem has been postponed.
-
-     The initial state of a PR is `open'.  *Note States of Problem
-     Reports: States.
-
-`>Responsible:'
-     (TEXT) The person responsible for this category.  GNATS retrieves
-     this information from the `categories' file (*note The
-     `categories' file: categories.).
-
-`>Arrival-Date:'
-     (TEXT) The time that this PR was received by GNATS.  The date is
-     provided automatically by GNATS.
-
-`>Audit-Trail:'
-     (MULTITEXT) Tracks related electronic mail as well as changes in
-     the `>State:' and `>Responsible:' fields with the sub-fields:
-
-    `State-Changed-<From>-<To>: OLDSTATE>-<NEWSTATE'
-          The old and new `>State:' field values.
-
-    `Responsible-Changed-<From>-<To>: OLDRESP>-<NEWRESP'
-          The old and new `>Responsible:' field values.
-
-    `State-Changed-By: NAME'
-    `Responsible-Changed-By: NAME'
-          The name of the maintainer who effected the change.
-
-    `State-Changed-When: TIMESTAMP'
-    `Responsible-Changed-When: TIMESTAMP'
-          The time the change was made.
-
-    `State-Changed-Why: REASON...'
-    `Responsible-Changed-Why: REASON...'
-          The reason for the change.
-
-     The `>Audit-Trail:' field also contains any mail messages received
-     by GNATS related to this PR, in the order received.
-
-`'
-     >Unformatted: (MULTITEXT) Any random text found outside the fields
-     in the original Problem Report.
-
-
-File: gnats.info,  Node: Invoking the tools,  Next: Management,  Prev: Introduction,  Up: Top
-
-Invoking the GNATS tools
-************************
-
-   The following programs comprise GNATS:
-
-User Utilities
---------------
-
-   These tools are used by the maintainers of a body of work (`send-pr'
-is also used by the end users of the product).
-
-`send-pr'
-     Used by anyone who has a problem with a body of work to submit a
-     report of the problem to the maintainers of that work (*note
-     Submitting Problem Reports: send-pr.).
-
-`query-pr'
-     Used by software maintainers to query the GNATS database (*note
-     Querying the database: query-pr.).
-
-`edit-pr'
-     Used by software maintainers to edit Problem Reports (to record new
-     data, to change the responsible party, etc.) (*note Editing
-     existing Problem Reports: edit-pr.).
-
-`view-pr'
-     Used by software maintainers to view individual Problem Reports
-     using Emacs (*note Viewing individual Problem Reports: view-pr.).
-
-Administrative Utilities
-------------------------
-
-   These tools are used by the GNATS administrator; see also *Note
-GNATS Administration: Management.  For complete explanations of these
-utilities, see *Note Administrative utilities: Admin utils.
-
-`mkcat'
-     Creates new categories (*note Adding a problem category: mkcat.).
-
-`rmcat'
-     Removes existing categories (*note Removing a problem category:
-     rmcat.).
-
-`gen-index'
-     Generates an up-to-date copy of the index used by `query-pr' and
-     `edit-pr' (*note The `index' file: index file.).  Use `gen-index'
-     to rebuild the index if it becomes corrupted, or if you need a
-     copy of the current index for some reason (*note Regenerating the
-     index: gen-index.).
-
-`mkdist'
-     Creates a distribution of the program `send-pr' for offsite
-     submitters of PRs (*note Configuring `send-pr' for the outside
-     world: mkdist.).
-
-Internal Utilities
-------------------
-
-   These tools are used internally by GNATS.  You should not need to
-run these by hand.  For complete explanations of these utilities, see
-*Note Internal utilities: Internal utils.
-
-`queue-pr'
-     Handles incoming bugs, first through a mail alias by queueing
-     incoming PRs as they arrive, and second as a periodic transfer
-     agent between the queue and the database.
-
-`file-pr'
-     Files Problem Reports as they come in.
-
-`at-pr'
-     Sends reminders to maintainers based on quoted response times.
-
-`pr-edit'
-     Used by `edit-pr' to error-check and submit edited Problem Reports
-     (also *note Editing existing Problem Reports: edit-pr.).
-
-`pr-addr'
-     Used by the `edit-pr' script to retrieve correct addresses from the
-     `responsible' file.
-
-   *Note Where GNATS lives: Locations.
-
-* Menu:
-
-* send-pr::           Submitting Problem Reports
-* edit-pr::           Editing existing Problem Reports
-* query-pr::          Querying the database
-* view-pr::           Viewing individual Problem Reports
-
-
-File: gnats.info,  Node: send-pr,  Next: edit-pr,  Up: Invoking the tools
-
-Submitting Problem Reports
-==========================
-
-   Use `send-pr' to submit Problem Reports to the database.  `send-pr'
-is both a shell script and a Lisp program for GNU Emacs; both
-implementations provide a template for submitters to complete.  In most
-cases, `send-pr' can determine intelligent default values for several
-fields, partially automating the bug-reporting process.
-
-   *Note Configuring `send-pr' for the outside world: mkdist, for
-information on distributing a version of `send-pr' customized with your
-site's configuration.
-
-   You can invoke `send-pr' from a shell prompt or from within GNU
-Emacs using `M-x send-pr'.
-
-* Menu:
-
-* using send-pr::             Creating new Problem Reports
-* send-pr in Emacs::          Using send-pr from within Emacs
-* send-pr from the shell::    Invoking send-pr from the shell
-* Helpful hints::
-
-
-File: gnats.info,  Node: using send-pr,  Next: send-pr in Emacs,  Up: send-pr
-
-Creating new Problem Reports
-----------------------------
-
-   Invoking `send-pr' presents a PR "template" with a number of fields
-already filled in.  Complete the template as thoroughly as possible to
-make a useful bug report.  Submit only one bug with each PR.
-
-   A template consists of three sections:
-
-"Comments"
-     The top several lines of a blank template consist of a series of
-     comments that provide some basic instructions for completing the
-     Problem Report, as well as a list of valid entries for the
-     `>Category:' field.  These comments are all preceded by the string
-     `SEND-PR:' and are erased automatically when the PR is submitted.
-     The instructional comments within `<' and `>' are also removed.
-     (Only these comments are removed; lines you provide that happen to
-     have those characters in them, such as examples of shell-level
-     redirection, are not affected.)
-
-"Mail Header"
-     `send-pr' creates a standard mail header.  `send-pr' completes all
-     fields except the `Subject:' line with default values.  (*Note
-     Problem Report format: Fields.)
-
-"GNATS fields"
-     These are the informational fields that GNATS uses to route your
-     Problem Report to the responsible party for further action.  They
-     should be filled out as completely as possible.  (*Note Problem
-     Report format: Fields.  Also see *Note Helpful hints: Helpful
-     hints.)
-
-   The default template contains your preconfigured `>Submitter-Id:'.
-`send-pr' attempts to determine values for the `>Originator:' and
-`>Organization:' fields (*note Problem Report format: Fields.).
-`send-pr' will set the `>Originator:' field to the value of the `NAME'
-environment variable if it has been set; similarly, `>Organization:'
-will be set to the value of `ORGANIZATION'.  `send-pr' also attempts to
-find out some information about your system and architecture, and
-places this information in the `>Environment:' field if it finds any.
-
-   You may submit problem reports to different Support Sites from the
-default site by specifying the alternate site when you invoke
-`send-pr'.  Each `site' has its own list of categories for which it
-accepts Problem Reports.
-
-   `send-pr' also provides the mail header section of the template with
-default values in the `To:', `From:', and `Reply-To:' fields.  The
-`Subject:' field is empty.
-
-   The template begins with a comment section:
-
-     SEND-PR: -*- send-pr  -*-
-     SEND-PR: Lines starting with `SEND-PR' will be removed
-     SEND-PR: automatically as well as all comments (the text
-     SEND-PR: below enclosed in `<' and `>').
-     SEND-PR:
-     SEND-PR: Please consult the document `Reporting Problems
-     SEND-PR: Using send-pr' if you are not sure how to fill out
-     SEND-PR: a problem report.
-     SEND-PR:
-     SEND-PR: Choose from the following categories:
-
-and also contains a list of valid `>Category:' values for the Support
-Site to whom you are submitting this Problem Report.  One (and only
-one) of these values should be placed in the `>Category:' field.
-
-   The mail header is just below the comment section.  Fill out the
-`Subject:' field, if it is not already completed using the value of
-`>Synopsis:'.  The other mail header fields contain default values.
-
-     To: SUPPORT-SITE
-     Subject: *complete this field*
-     From: YOUR-LOGIN@YOUR-SITE
-     Reply-To: YOUR-LOGIN@YOUR-SITE
-     X-send-pr-version: send-pr 3.101
-
-where SUPPORT-SITE is an alias for the Support Site you wish to submit
-this PR to.
-
-   The rest of the template contains GNATS fields.  Each field is
-either automatically completed with valid information (such as your
-`>Submitter-Id:') or contains a one-line instruction specifying the
-information that field requires in order to be correct.  For example,
-the `>Confidential:' field expects a value of `yes' or `no', and the
-answer must fit on one line; similarly, the `>Synopsis:' field expects
-a short synopsis of the problem, which must also fit on one line.  Fill
-out the fields as completely as possible.  *Note Helpful hints: Helpful
-hints, for suggestions as to what kinds of information to include.
-
-   In this example, words in *italics* are filled in with
-pre-configured information:
-
-     >Submitter-Id: *your submitter-id*
-     >Originator:   *your name here*
-     >Organization:
-         *your organization*
-     >Confidential:<[ yes | no ] (one line)>
-     >Synopsis:    <synopsis of the problem (one line)>
-     >Severity:    <[non-critical | serious | critical](one line)>
-     >Priority:    <[ low | medium | high ] (one line)>
-     >Category:    <name of the product (one line)>
-     >Class:       <[sw-bug | doc-bug | change-request | support]>
-     >Release:     <release number (one line)>
-     >Environment:
-              <machine, os, target, libraries (multiple lines)>
-     
-     >Description:
-            <precise description of the problem (multiple lines)>
-     >How-To-Repeat:
-            <code/input/activities to reproduce (multiple lines)>
-     >Fix:
-            <how to correct or work around the problem, if known
-             (multiple lines)>
-
-   When you finish editing the Problem Report, `send-pr' mails it to
-the address named in the `To:' field in the mail header.  `send-pr'
-checks that the complete form contains a valid `>Category:'.
-
-   If your PR has an invalid value in one of the ENUMERATED fields
-(*note Problem Report format: Fields.), `send-pr' places the PR in a
-temporary file named `/tmp/pbadNNNN' on your machine.  NNNN is the
-process identification number given to your current `send-pr' session.
-If you are running `send-pr' from the shell, you are prompted as to
-whether or not you wish to try editing the same Problem Report again.
-If you are running `send-pr' from Emacs, the Problem Report is placed
-in the buffer `*send-pr-error*'; you can edit this file and then submit
-it with
-
-     M-x gnats-submit-pr
-
-   Any further mail concerning this Problem Report should be
-carbon-copied to the GNATS mailing address as well, with the category
-and identification number in the `Subject:' line of the message.
-
-     Subject: Re: PR CATEGORY/GNATS-ID: ORIGINAL MESSAGE SUBJECT
-
-Messages which arrive with `Subject:' lines of this form are
-automatically appended to the Problem Report in the `>Audit-Trail:'
-field in the order received.
-
-
-File: gnats.info,  Node: send-pr in Emacs,  Next: send-pr from the shell,  Prev: using send-pr,  Up: send-pr
-
-Using `send-pr' from within Emacs
----------------------------------
-
-   You can use an interactive `send-pr' interface from within GNU Emacs
-to fill out your Problem Report.  We recommend that you familiarize
-yourself with Emacs before using this feature (*note Introduction:
-(emacs)Introduction.).
-
-   Call `send-pr' with `M-x send-pr'.(1)  `send-pr' responds with a
-Problem Report template preconfigured for the Support Site from which
-you received `send-pr'.  (If you use `send-pr' locally, the default
-Support Site is probably your local site.)
-
-   You may also submit problem reports to different Support Sites from
-the default site.  To use this feature, invoke `send-pr' with
-
-     C-u M-x send-pr
-
-   `send-pr' prompts you for the name of a SITE.  SITE is an alias on
-your local machine which points to an alternate Support Site.
-
-   `send-pr' displays the template and prompts you in the minibuffer
-with the line:
-     >Category: other
-
-Delete the default value `other' *in the minibuffer* and replace it
-with the keyword corresponding to your problem (the list of valid
-categories is in the topmost section of the PR template).  For example,
-if the problem you wish to report has to do with the GNU C compiler,
-and your support organization accepts bugs submitted for this program
-under the category `gcc', delete `other' and then type `gcc[<RET>]'.
-`send-pr' replaces the line
-
-     >Category:       <name of the product (one line)>
-
-in the template with
-
-     >Category:       gcc
-
-and moves on to another field.
-
-   `send-pr' provides name completion in the minibuffer.  For instance,
-you can also type `gc[<TAB>]', and `send-pr' attempts to complete the
-entry for you.  Typing `g[<TAB>]' may not have the same effect if
-several possible entries begin with `g'.  In that case `send-pr' cannot
-complete the entry because it cannot determine whether you mean `gcc'
-or, for example, `gdb', if both of those are possible categories.
-`send-pr' continues to prompt you for a valid entry until you enter one.
-
-   `send-pr' prompts you interactively to enter each field for which
-there is a range of specific choices.  If you attempt to enter a value
-which is not in the range of acceptable entries, `send-pr' responds
-with `[No match]' and allows you to change the entry until it contains
-an acceptable value.  This avoids unusable information (at least in
-these fields) and also avoids typographical errors which could cause
-problems later.
-
-   `send-pr' prompts you for the following fields:
-
-     >Category:
-     >Confidential: (*default*:  no)
-     >Severity:     (*default*:  serious)
-     >Priority:     (*default*:  medium)
-     >Class:        (*default*:  sw-bug)
-     >Release:
-     >Synopsis:     (*this value is copied to `Subject:'*)
-
-After you complete these fields, `send-pr' places the cursor in the
-`>Description:' field and displays the message
-
-     To send the problem report use: C-c C-c
-
-in the minibuffer.  At this point, edit the file in the main buffer to
-reflect your specific problem, putting relevant information in the
-proper fields.
-
-   `send-pr' provides a few key bindings to make moving around in a
-template buffer more simple:
-
-`C-c C-f'
-`M-x change-field'
-     Changes the field under the cursor.  `edit-pr' prompts you for a
-     new value.
-
-`M-C-b'
-`M-x gnats-backward-field'
-     Moves the cursor to the beginning of the value of the current
-     field.
-
-`M-C-f'
-`M-x gnats-forward-field'
-     Moves the cursor to the end of the value of the current field.
-
-`M-p'
-`M-x gnats-previous-field'
-     Moves the cursor back one field to the beginning of the value of
-     the previous field.
-
-`M-n'
-`M-x gnats-next-field'
-     Moves the cursor forward one field to the beginning of the value
-     of the next field.
-
-   `send-pr' takes over again when you type `C-c C-c' to send the
-message.  `send-pr' reports any errors in a separate buffer, which
-remains in existence until you send the PR properly (or, of course,
-until you explicitly kill the buffer).
-
-   For detailed instructions on using Emacs, see *Note Introduction:
-(emacs)Introduction.
-
-   ---------- Footnotes ----------
-
-   (1) If typing `M-x send-pr' doesn't work, see your system
-administrator for help loading `send-pr' into Emacs.
-
-
-File: gnats.info,  Node: send-pr from the shell,  Next: Helpful hints,  Prev: send-pr in Emacs,  Up: send-pr
-
-Invoking `send-pr' from the shell
----------------------------------
-
-     send-pr [ SITE ]
-             [ -f PROBLEM-REPORT | --file PROBLEM-REPORT ]
-             [ -t MAIL-ADDRESS | --to MAIL-ADDRESS ]
-             [ --request-id ]
-             [ -L | --list ] [ -P | --print ]
-             [ -V | --version] [ -h | --help ]
-
-   SITE is an alias on your local machine which points to an address
-used by a Support Site.  If this argument is not present, the default
-SITE is usually the site which you received `send-pr' from, or your
-local site if you use GNATS locally.
-
-   Invoking `send-pr' with no options calls the editor named in your
-environment variable `EDITOR' on a default PR template.  If the
-environment variable `PR_FORM' is set, its value is used as a file name
-which contains a valid template.  If `PR_FORM' points to a missing or
-unreadable file, or if the file is empty, `send-pr' generates an error
-message and opens the editor on a default template.
-
-`-f PROBLEM-REPORT'
-`--file PROBLEM-REPORT'
-     Specifies a file, PROBLEM-REPORT, where a completed Problem Report
-     already exists.  `send-pr' sends the contents of the file without
-     invoking an editor.  If PROBLEM-REPORT is `-', `send-pr' reads
-     from standard input.
-
-`-t MAIL-ADDRESS'
-`--to MAIL-ADDRESS'
-     Sends the PR to MAIL-ADDRESS. The default is preset when `send-pr'
-     is configured.  *This option is not recommended*; instead, use the
-     argument SITE on the command line.
-
-`-c MAIL-ADDRESS'
-`--cc MAIL-ADDRESS'
-     Places MAIL-ADDRESS in the `Cc:' header field of the message to be
-     sent.
-
-`--request-id'
-     Sends a request for a `>Submitter-Id:' to the Support Site.
-
-`-L'
-`--list'
-     Prints the list of valid `>Category:' values on standard output.
-     No mail is sent.
-
-`-s SEVERITY'
-`--severity SEVERITY'
-     Sets the initial value of the `>Severity:' field to SEVERITY.
-
-`-P'
-`--print'
-     Displays the PR template.  If the variable `PR_FORM' is set in your
-     environment, the file it specifies is printed.  If `PR_FORM' is not
-     set, `send-pr' prints the standard blank form.  If the file
-     specified by `PR_FORM' doesn't exist, `send-pr' displays an error
-     message.  No mail is sent.
-
-`-V'
-`--version'
-     Displays the `send-pr' version number and a usage summary.  No mail
-     is sent.
-
-`-h'
-`--help'
-     Displays a usage summary for `send-pr'.  No mail is sent.
-
-
-File: gnats.info,  Node: Helpful hints,  Prev: send-pr from the shell,  Up: send-pr
-
-Helpful hints
--------------
-
-   There is no orthodox standard for submitting effective bug reports,
-though you might do well to consult the section on submitting bugs for
-
-   GNU `gcc' in *Note Reporting Bugs: (gcc)Bugs, by Richard Stallman.
-This section contains instructions on what kinds of information to
-include and what kinds of mistakes to avoid.
-
-   In general, common sense (assuming such an animal exists) dictates
-the kind of information that would be most helpful in tracking down and
-resolving problems in software.
-   * Include anything *you* would want to know if you were looking at
-     the report from the other end.  There's no need to include every
-     minute detail about your environment, although anything that might
-     be different from someone else's environment should be included
-     (your path, for instance).
-
-   * Narratives are often useful, given a certain degree of restraint.
-     If a person responsible for a bug can see that A was executed, and
-     then B and then C, knowing that sequence of events might trigger
-     the realization of an intermediate step that was missing, or an
-     extra step that might have changed the environment enough to cause
-     a visible problem.  Again, restraint is always in order ("I set
-     the build running, went to get a cup of coffee (Columbian, cream
-     but no sugar), talked to Sheila on the phone, and then THIS
-     happened...") but be sure to include anything relevant.
-
-   * Richard Stallman writes, "The fundamental principle of reporting
-     bugs usefully is this: *report all the facts*.  If you are not sure
-     whether to state a fact or leave it out, state it!"  This holds
-     true across all problem reporting systems, for computer software
-     or social injustice or motorcycle maintenance.  It is especially
-     important in the software field due to the major differences
-     seemingly insignificant changes can make (a changed variable, a
-     missing semicolon, etc.).
-
-   * Submit only *one* problem with each Problem Report.  If you have
-     multiple problems, use multiple PRs.  This aids in tracking each
-     problem and also in analyzing the problems associated with a given
-     program.
-
-   * It never hurts to do a little research to find out if the bug
-     you've found has already been reported.  Most software releases
-     contain lists of known bugs in the Release Notes which come with
-     the software; see your system administrator if you don't have a
-     copy of these.
-
-   * The more closely a PR adheres to the standard format, the less
-     interaction is required by a database administrator to route the
-     information to the proper place.  Keep in mind that anything that
-     requires human interaction also requires time that might be better
-     spent in actually fixing the problem.  It is therefore in
-     everyone's best interest that the information contained in a PR be
-     as correct as possible (in both format and content) at the time of
-     submission.
-
-
-File: gnats.info,  Node: edit-pr,  Next: query-pr,  Prev: send-pr,  Up: Invoking the tools
-
-Editing existing Problem Reports
-================================
-
-   Use `edit-pr' to make changes to existing PRs in the database.
-`edit-pr' is both a shell script and a Lisp program for GNU Emacs.
-Both implementations are essentially identical, though the Emacs
-interface provides interactive prompting for some of the fields.
-
-   `edit-pr' first examines the PR you wish to edit and locks it if it
-is not already locked.  This is to prevent you from editing a PR at the
-same time as another user.  If the PR you wish to edit is already in the
-process of being edited, `edit-pr' tells you the name of the person who
-owns the lock.
-
-   You may edit any field in the database that you wish.  We recommend
-that you avoid deleting any information in the TEXT and MULTITEXT
-fields (such as `>Description:' and `>How-To-Repeat:' (*note Problem
-Report format: Fields.).  We also recommend that you record the final
-solution to the problem in the `>Fix:' field for future reference.
-
-   If you change the `>Responsible:' field, `edit-pr' prompts you to
-supply a reason for the change.  `edit-pr' then mails copies of the
-change message to the previous responsible party, and to the new
-responsible party.  The change is then recorded in the `>Audit-Trail:'
-section of the PR as follows:
-
-`Responsible-Changed-<From>-<To>': The value change, supplied
-     automatically by `edit-pr'.
-
-`Responsible-Changed-By': Your name here, supplied
-     automatically by `edit-pr'.
-
-`Responsible-Changed-When': The current date, supplied
-     automatically by `edit-pr'.
-
-`Responsible-Changed-Why': Your reason for the change; you
-     are prompted for this.
-
-   If you change the `>State:' field, you are prompted to supply a
-reason for the change.  Copies of the change message are then mailed to
-the responsible party, and to the original submitter of the Problem
-Report.  The change is then recorded in the `Audit-Trail' section of
-the PR as follows:
-
-`State-Changed-<From>-<To>': The value change, supplied
-     automatically by `edit-pr'.
-
-`State-Changed-By': Your name here, supplied
-     automatically by `edit-pr'.
-
-`State-Changed-When': The current date, supplied
-     automatically by `edit-pr'.
-
-`State-Changed-Why': Your reason for the change; you are
-     prompted for this.
-
-   The PR is then resubmitted to the database, and the index is updated
-(*note The `index' file: index file.).  For information on `pr-edit',
-the main driver for `edit-pr', see *Note Internal utilities: Internal
-utils.
-
-* Menu:
-
-* edit-pr in Emacs::        Using `edit-pr' from within Emacs
-* edit-pr from the shell::  Invoking `edit-pr' from the shell
-

texi/gnats.info-2

-This is Info file gnats.info, produced by Makeinfo version 1.68 from
-the input file gnats.texi.
-
-START-INFO-DIR-ENTRY
-* Keeping Track: (gnats).        GNU Problem Report Management System
-END-INFO-DIR-ENTRY
-
-   Copyright (C) 1993, 1995 Free Software Foundation, Inc.
-
-   Permission is granted to make and distribute verbatim copies of this
-manual provided the copyright notice and this permission notice are
-preserved on all copies.
-
-   Permission is granted to copy and distribute modified versions of
-this manual under the conditions for verbatim copying, provided also
-that the entire resulting derived work is distributed under the terms
-of a permission notice identical to this one.
-
-   Permission is granted to copy and distribute translations of this
-manual into another language, under the above conditions for modified
-versions.
-
-
-File: gnats.info,  Node: edit-pr in Emacs,  Next: edit-pr from the shell,  Up: edit-pr
-
-Using `edit-pr' from within Emacs
----------------------------------
-
-   Call `edit-pr' from within Emacs with `M-x edit-pr'(1).  When
-`edit-pr' prompts you for a PR identification number, type the number
-of the PR you wish to edit.
-
-   If the PR is locked, Emacs announces the login name of the person who
-has locked the file.  If not, `M-x edit-pr' locks the PR, loads it into
-a buffer named `*edit-pr*', and places the cursor in the `>Number:'
-field.  (*Do not change this field*.)
-
-   Edit the PR to reflect correct information.  Resubmit the PR to the
-database using `C-c C-c' (see below).
-
-   The easiest way to edit a PR from Emacs is to use the special key
-bindings provided.  These are:
-
-`C-c C-c'
-`M-x gnats-submit-pr'
-     Saves and resubmits the PR currently being edited.  Do this when
-     you finish editing the PR; if you simply kill the buffer, your
-     changes are lost.
-
-`C-x C-s'
-`M-x save-buffer'
-     Saves the current buffer tp a file.  You are prompted for a
-     filename.  This is not a special key binding, but at one point in
-     the history of GNATS it was used to resubmit the PR (i.e., it was
-     bound to `M-x gnats-submit-pr').  `C-x C-s' now simply saves a
-     copy of the PR.  This command *does not* resubmit the PR to the
-     database.  Use `C-c C-c' to resubmit the PR.
-
-`C-x k'
-`M-x gnats:kill-buffer (*use this only with Emacs 18*)'
-`M-x kill-buffer'
-     Kills the current buffer (destroying all changes) and unlocks the
-     current PR.  Use this to back out of a change without affecting the
-     database.
-
-`C-c C-u'
-`M-x unlock-pr'
-     Unlocks a PR that you have locked.  Use this if you have a locked
-     PR from a failed editing session.  You are prompted for the
-     GNATS-ID of a PR to unlock.
-
-`C-c C-q'
-
-`M-x unlock-buffer'
-     Removes the lock on the current PR, allowing others to edit it.
-     The buffer remains active and non-writeable.  To relock a PR,
-     simply type `e' in the buffer containing the Problem Report.
-
-`C-c C-e'
-`M-x edit-pr'
-     Runs `edit-pr' in a new buffer.
-
-`C-c C-f'
-`M-x change-field'
-     Changes the field under the cursor.  `edit-pr' prompts you for a
-     new value.  If you use
-
-          C-u C-c C-f  *or*
-          C-u M-x change-field
-
-     you are prompted for a field to change.
-
-`C-c C-a'
-`M-x gnats-mail-reply'
-     Sends mail to the originator of this PR, using the address in the
-     `From:' field of the mail header.  The `Subject', `To:', and `Cc:'
-     fields are constructed from the Problem Report currently being
-     edited.  Edit the message, and use `C-c C-c' to send it.
-
-`C-c RET'
-`C-c C-m'
-`M-x gnats-mail-other-window'
-     Splits the current window, and starts a mail message.  The
-     `Subject:' field is constructed from the Problem Report currently
-     being edited.  Edit the message, and use `C-c C-c' to send it.
-
-`C-c C-r'
-`M-x gnats-responsible-change-from-to'
-     Changes the `>Responsible:' field.  `edit-pr' prompts you for the
-     new responsible person, and for a message describing the reason for
-     the change.  When you type `C-c C-c' to resubmit the PR, the
-     cursor is placed in a mail buffer containing a copy of the change.
-     You can then edit this buffer and type `C-c C-c' again to send the
-     mail.
-
-`C-c C-s'
-`M-x gnats-state-change-from-to'
-     Changes the `>State:' field.  `edit-pr' prompts you for the new
-     state, and for a message describing the reason for the change.
-     When you type `C-c C-c' to resubmit the PR, the cursor is placed in
-     a mail buffer containing a copy of the change.  You can then edit
-     this buffer and type `C-c C-c' again to send the mail.
-
-`C-c C-t'
-`M-x category-change-from-to'
-     Changes the `>Category:' field of the PR.  `edit-pr' prompts you
-     for the new category.  `edit-pr' also prompts you with the question
-
-          Update the >Responsible field?
-
-     Type `y' to change the value of the `>Responsible:' field to the
-     name of the party responsible for the new category.  Type `n' to
-     keep the current value of `>Responsible:'.
-
-`M-C-b'
-`M-x gnats-backward-field'
-     Moves the cursor to the beginning of the value of the current
-     field.
-
-`M-C-f'
-`M-x gnats-forward-field'
-     Moves the cursor to the end of the value of the current field.
-
-`M-p'
-`M-x gnats-previous-field'
-     Moves the cursor back one field to the beginning of the value of
-     the previous field.
-
-`M-n'
-`M-x gnats-next-field'
-     Moves the cursor forward one field to the beginning of the value
-     of the next field.
-
-   ---------- Footnotes ----------
-
-   (1) If typing `M-x edit-pr' doesn't work, see your system
-administrator for help loading `edit-pr' into Emacs.
-
-
-File: gnats.info,  Node: edit-pr from the shell,  Prev: edit-pr in Emacs,  Up: edit-pr
-
-Invoking `edit-pr' from the shell
----------------------------------
-
-   The usage for the `edit-pr' shell script is:
-
-     edit-pr GNATS-ID [ -V | --version ] [ -h | --help ]
-
-You must first determine which PR you want to edit.  The options are:
-
-`-V *or* --version'
-     Prints the version number for `edit-pr'.
-
-`-h *or* --help'
-     Prints the usage for `edit-pr'.
-
-   `edit-pr' calls the editor specified in your environment variable
-`EDITOR' on a temporary copy of that PR.  (If you don't have the
-variable `EDITOR' defined in your environment, the default editor `vi'
-is used.)
-
-   Edit the PR, changing any relevant fields or adding to existing
-information.  When you exit the editor, `edit-pr' prompts you on
-standard input for a reason if you've changed either the
-`>Responsible:' field or the `>State:' field.  `edit-pr' tracks the
-information you provide when changing either of these two fields, along
-with the change that occurred, your name, and the time of change in the
-`>Audit-Trail:' field.
-
-
-File: gnats.info,  Node: query-pr,  Next: view-pr,  Prev: edit-pr,  Up: Invoking the tools
-
-Querying the database
-=====================
-
-   Obtain information from the database by using the program
-`query-pr'. `query-pr' uses search parameters you provide to find
-matching Problem Reports in the database.  You can invoke `query-pr'
-from the shell or from within Emacs.  `query-pr' uses the same
-arguments whether it is invoked from the shell or from Emacs.
-
-   All arguments and options to `query-pr' are optional.  If you do not
-specify a PR identification number and do not give any search
-parameters, `query-pr' displays the entire database.  All arguments are
-considered identification numbers of Problem Reports to display.  Any
-number of options can be given (though some make no sense when
-specified on the same command line); all are connected with a logical
-`AND'.
-
-* Menu:
-
-* Invoking query-pr::
-* Example queries::
-* Reporting::
-
-
-File: gnats.info,  Node: Invoking query-pr,  Next: Example queries,  Up: query-pr
-
-Invoking `query-pr'
--------------------
-
-   From the shell, simply type `query-pr', followed by any search
-parameters you wish to exercise.  From Emacs, type `M-x query-pr'.
-`query-pr' prompts you for search parameters in the minibuffer.
-
-   `query-pr' can also be accessed by electronic mail, if your version
-of GNATS is configured for this.  To use this feature, simply send mail
-to the address `query-pr@YOUR-SITE' with command line arguments or
-options in the `Subject:' line of the mail header.  GNATS replies to
-your mail with the results of your query.  The default settings for the
-`query-pr' mail server are
-
-     --restricted --state="open|analyzed|feedback|suspended"
-
-To override the `--state' parameter, specify `--state=STATE' in the
-`Subject:' line of the mail header.  You can not query on confidential
-Problem Reports by mail.
-
-   The usage for `query-pr' is:
-
-     query-pr [ GNATS-ID ]
-              [ -c CATEGORY | --category=CATEGORY ]
-              [ -s STATE | --state=STATE ]
-              [ -r RESPONSIBLE | --responsible=RESPONSIBLE ]
-              [ -S SUBMITTER | --submitter=SUBMITTER ]
-              [ -C [ YES | NO ] | --confidential=[ YES | NO ] ]
-              [ -e SEVERITY | --severity=SEVERITY ]
-              [ -p PRIORITY | --priority=PRIORITY ]
-              [ -O ORIGINATOR | --originator=ORIGINATOR ]
-              [ -L CLASS | --class=CLASS ]
-              [ -t TEXT | --text=TEXT ]
-              [ -m TEXT | --multitext=TEXT ]
-              [ -R | --restricted ]
-              [ -F | --full ] [ -q | --summary ] [ -i | --sql ]
-              [ -P | --print-path ]
-              [ -d DIRECTORY | --directory=DIRECTORY ]
-              [ -o OUTFILE | --output=OUTFILE ]
-              [ -V | --version ] [ -h | --help ]
-
-   If you run `query-pr' from within Emacs, you can use
-
-     C-x `     *or*       M-x next-error
-
-to scroll through Problem Reports one by one after the search is
-finished.
-
-Search criteria
----------------
-
-   The following arguments and options specify search criteria.  The
-lack of a criterion indicates that all values for the corresponding
-field are valid for the search.  Regular expressions may be used as
-arguments to search criteria options; see *Note Querying using regular
-expressions: Regexps.
-
-   Using an argument to `query-pr' specifies the most stringent search
-criteria, that of a single PR.
-
-`GNATS-ID'
-     The identification number of the PR you wish to view, as shown in
-     the `>Number:' field.  Any number of GNATS-ID arguments may be
-     given.
-
-`-c CATEGORY'
-`--category=CATEGORY'
-     Search only for PRs with a `>Category:' value of CATEGORY.  For a
-     list of valid categories, type `send-pr -L' from the shell.
-
-`-s STATE'
-`--state=STATE'
-     Search only for PRs with a `>State:' value of STATE.  STATE must
-     be one of: `open', `analyzed', `feedback', `closed', or
-     `suspended'.
-
-     This field may be searched using regular expressions.  *Note
-     Querying using regular expressions: Regexps.  Also see *Note
-     Example queries: Example queries.
-
-`-r RESPONSIBLE'
-`--responsible=RESPONSIBLE'
-     Search only for PRs with a `>Responsible:' value of RESPONSIBLE.
-
-`-S SUBMITTER'
-`--submitter=SUBMITTER'
-     Search only for PRs with a `>Submitter:' value of SUBMITTER.
-
-`-C [YES | NO]'
-`--confidential=[YES | NO]'
-     Search only for PRs with a `>Confidential:' value of either YES or
-     NO.  If this option is not given, all PRs are eligible for the
-     search regardless of their confidentiality.
-
-`-e SEVERITY'
-`--severity=SEVERITY'
-     Search only for PRs with a `>Severity:' value of SEVERITY.
-     SEVERITY must be one of: `critical', `serious', or `non-critical'.
-
-`-p PRIORITY'
-`--priority=PRIORITY'
-     Search only for PRs with a `>Priority:' value of PRIORITY.
-     PRIORITY must be one of: `high', `medium', or `low'.
-
-`-O ORIGINATOR'
-`--originator=ORIGINATOR'
-     Search only for PRs with an `>Originator:' value of ORIGINATOR.
-
-     Since this option does not reference the index, queries using it
-     finish much faster if you also use another search criterion that
-     *is* part of the index (*note The `index' file: index file.).
-
-`-L CLASS'
-`--class=CLASS'
-     Search only for PRs with a `>Class:' value of CLASS.  Since this
-     option does not reference the index, queries using it finish much
-     faster if you also use another search criterion that *is* part of
-     the index (*note The `index' file: index file.).
-
-`-t TEXT'
-`--text=TEXT'
-     Search the TEXT fields in the database for the regular expression
-     TEXT.  TEXT fields include the following (the `>' and `:' Problem
-     Report fieldname delimiters have been removed for the sake of
-     brevity and readability):
-
-          Submitter-Id   Originator     Synopsis
-          Category       Release        Responsible
-          Arrival-Date
-
-     *Note Querying using regular expressions: Regexps.
-
-     Queries using this option can be slow.  Since this option does not
-     reference the index, queries using it finish much faster if you
-     also use another search criterion that *is* part of the index
-     (*note The `index' file: index file.).
-
-`-m TEXT'
-
-`--multitext=TEXT'
-     Search the MULTITEXT fields in the database for the regular
-     expression TEXT.  MULTITEXT fields include the following (again,
-     the fieldname delimiters `>' and `:' have been omitted):
-
-          Organization   Environment    Description
-          How-To-Repeat  Fix            Audit-Trail
-          Unformatted
-
-     *Note Querying using regular expressions: Regexps.
-
-     Queries using this option can be very slow.  Since this option
-     does not reference the index, queries using it finish much faster
-     if you also use another search criterion that *is* part of the
-     index (*note The `index' file: index file.).
-
-`-R'
-`--restricted'
-     Omit from the search path PRs whose `>Confidential:' fields contain
-     the value `yes'.  This is equivalent to
-
-          query-pr --confidential=no
-
-     and also disallows the use of the options `--outfile=OUTFILE' and
-     `--directory=DIRECTORY'.  This option is used with the
-     `mail-query' tool.
-
-`-x'
-`--skip-closed'
-     Omit closed PRs from the search path.  This option is ignored if
-     you also use `-s STATE' or `--state=STATE'.
-
-Output format
--------------
-
-   Use the following options to select the format in which the Problem
-Report is printed.  Use only one of these options for a given search.
-If you do not specify one of these options, a header(1) for the Problem
-Reports meeting the search criteria is printed.
-
-`-F'
-`--full'
-     Prints all fields in the Problem Report rather than just summary
-     information.
-
-`-q'
-`--summary'
-     Print a short single-line summary of PR information, delimited by
-     whitespace, including the following fields in order (the `>' and
-     `:' Problem Report fieldname delimiters have been removed for the
-     sake of brevity and readability):
-
-          Number         Responsible    Category
-          State          Severity       Priority
-          Submitter-Id   Synopsis
-
-`-i'
-`--sql'
-     Prints information on a single line with fields delimited by pipes
-     (`|'), which can be uploaded into a relational database.  When you
-     use this option, `query-pr' outputs ENUMERATED fields numerically
-     rather than textually; see *Note Reporting on groups of Problem
-     Reports: Reporting.
-
-     `query-pr -i' outputs the following fields, in order (again, the
-     fieldname delimiters `>' and `:' have been omitted):
-
-          Number         Category       Synopsis
-          Confidential   Severity       Priority
-          Responsible    State          Class
-          Submitter-Id   Arrival-Date   Originator
-          Release
-
-     When you use the `-i' option, `query-pr' outputs the ENUMERATED
-     fields in the database, namely `>Severity:', `>Priority:',
-     `>State:', and `>Class:', as numbers rather than text.  *Note
-     Reporting on groups of Problem Reports: Reporting, for details.
-
-Other options
--------------
-
-   `query-pr' also accepts the following options:
-
-`-P'
-`--print-path'
-     Prints the path which `query-pr' used to find the current PR.  A
-     line of the form `DIRECTORY/NUMBER:NUMBER' is printed before each
-     PR.  This option is automatically used from within Emacs to
-     facilitate scrolling through groups of PRs with `C-x `'.
-
-`-d DIRECTORY'
-`--directory=DIRECTORY'
-     Changes the search directory to DIRECTORY from GNATS_ROOT.
-
-`-o OUTFILE'
-`--output=OUTFILE'
-     Prints all output to OUTFILE rather than to the standard output.
-
-`-V'
-`--version'
-     Prints the version number for `query-pr'.
-
-`-h'
-`--help'
-     Prints the usage for `query-pr'.
-
-   ---------- Footnotes ----------
-
-   (1) A "header" includes the mail header fields as well as the
-following fields: `>Number:', `>Category:', `>Synopsis:',
-`>Confidential:', `>Severity:', `>Priority:', `>Responsible:',
-`>State:', `>Class:', `>Submitter-Id:', `>Originator:', `>Release:', and
-`>Arrival-Date:'.  For suggestions on using alternate output formats in
-database reports, see *Note Reporting: Reporting.
-
-
-File: gnats.info,  Node: Example queries,  Next: Reporting,  Prev: Invoking query-pr,  Up: query-pr
-
-Example queries
----------------
-
-   The following simple query:
-
-     query-pr --category=rats --responsible=fred --state=analyzed
-
-yields all PRs in the database which contain the field values:
-
-     >Category:     rats         *and*
-     >Responsible:  fred         *and*
-     >State:        analyzed
-
-   The following query:
-
-     query-pr --state="o|a"
-
-yields all PRs in the database whose `>State:' values match either
-`open' or `analyzed' (*note Querying using regular expressions:
-Regexps..  This search is useful as a daily report that lists all
-Problem Reports which require attention.
-
-   The report can be further altered using an alternate output format
-for `query-pr'; see *Note Reporting on groups of Problem Reports:
-Reporting.  A more fine-grained report may be obtained by specifying
-more search parameters, e.g. narrowing the search down by `>Submitter:'
-or by `>Responsible:'.
-
-   The following query:
-
-     query-pr --text="The quick.*brown fox"
-
-yields all PRs whose TEXT fields contain the text `The quick' followed
-by `brown fox' within the same field.  *Note Querying using regular
-expressions: Regexps.
-
-
-File: gnats.info,  Node: Reporting,  Prev: Example queries,  Up: query-pr
-
-Reporting on groups of Problem Reports
---------------------------------------
-
-   There currently exists no separate reporting mechanism in GNATS from
-`query-pr'.  However, the `-q' and `-i' options to `query-pr' allow for
-easy reporting.
-
-   For example, a report on the current open Problem Reports in the
-database can be obtained using `awk' with
-
-     query-pr -q | awk '{print $3 "/" $1 ": " $4}'
-
-which yields a list of the form
-
-     CATEGORY/GNATS-ID: STATE
-     *etc...*
-
-For example:
-
-     sprockets/123: open
-     widgets/456: analyzed
-     *etc...*
-
-The `-i' option to `query-pr' yields output delimited by pipes (`|').
-This results in the following:
-
-     GNATS-ID|CATEGORY|SYNOPSIS|CONFIDENTIAL|\
-     SEVERITY|PRIORITY|RESPONSIBLE|STATE|CLASS|\
-     SUBMITTER-ID|ARRIVAL-DATE|ORIGINATOR|RELEASE
-
-   A report on Problem Reports in the database that are currently
-`open' or `analyzed' might resemble the following (the example is split
-into two lines in order to fit onto the page; it is intended to be
-typed on one command line):
-
-     query-pr -i -s "o|a" | \
-       awk -F\| '{print $1 "  " $2 "  " $8 "  " $3}'
-
-which yields
-
-     GNATS-ID  CATEGORY  STATE  RESPONSIBLE SYNOPSIS
-     *etc...*
-
-For example:
-
-     123  sprockets  1  fred    The sprockets program gives bad output
-     456  widgets    2  barney  The foo widget doesn't work with 'bar'
-     789  widgets    1  wilma   The 'baz' widget is broken
-
-When you use the `-i' option, `query-pr' outputs the ENUMERATED fields
-in the database, namely `>Severity:', `>Priority:', `>State:', and
-`>Class:', as numbers rather than text.  In the example above, a
-`>State:' value of `1' means `open', `2' means `analyzed', and so forth.
-ENUMERATED fields are output according to the following paradigm:
-
-         >Severity:                   >Priority:
-     critical        1             high            1
-     serious         2             medium          2
-     non-critical    3             low             3
-     
-          >State:                      >Class:
-     open            1             sw-bug          1
-     analyzed        2             doc-bug         2
-     suspended       3             support         3
-     feedback        4             change-request  4
-     closed          5             mistaken        5
-                                   duplicate       6
-
-   This makes sorting on these values easy, when combined with `sort'.
-It is left as an exercise for the reader to figure out how to do this.
-
-
-File: gnats.info,  Node: view-pr,  Prev: query-pr,  Up: Invoking the tools
-
-Viewing individual Problem Reports
-==================================
-
-   Use `view-pr' from within Emacs to view individual Problem Reports.
-Invoke `view-pr' with
-
-     M-x view-pr
-
-   You are prompted to enter a Problem Report identification number
-(GNATS-ID).  You can also invoke `view-pr' with
-
-     C-u GNATS-ID M-x view-pr
-
-   `view-pr' allows you to view GNATS-ID.  This is identical to using
-
-     C-u GNATS-ID M-x query-pr
-
-   except that you may choose to edit the PR at any time by pressing
-`e'.
-
-
-File: gnats.info,  Node: Management,  Next: Installation,  Prev: Invoking the tools,  Up: Top
-
-GNATS Administration
-********************
-
-   In daily usage, GNATS is self-maintaining.  However, there are
-various administrative duties which need to be performed periodically:
-
-*emptying the `pending' directory*
-     If a Problem Report arrives with a `>Category:' value that is
-     unrecognized by the `categories' file, or if that field is missing,
-     GNATS places the PR in the `pending' directory (*note Where the
-     tools and utilities reside: Locations.).  GNATS has no way of
-     knowing which subdirectory the PR should be filed under.  GNATS
-     sends a notice to the `gnats-admin' and to the party responsible
-     for that submitter (as listed in the `submitters' file) when this
-     occurs.
-
-     To file these PRs, simply use `edit-pr' to repair the problematic
-     fields in each file in the `pending' directory.  Be sure to change
-     the `>Category:' field of the PR from `pending' to an appropriate
-     category.  In many cases the culprit is simply a typographical
-     error, although it may be necessary sometimes to contact the
-     submitter of the PR to decipher her or his intentions.
-
-     Should you run out of disk space, there may be an empty PR in the
-     `pending' directory.  In that case, look in the file
-     `GNATS_ROOT/gnats-adm/bug.log', which should still contain the
-     full message that was submitted.
-
-*adding new categories*
-     To add a new category, simply insert a new line in the
-     `categories' file and then run the program `mkcat'.
-
-     *Note*: this causes all category lists for `send-pr' (except the
-     one on the local machine) to become outdated.  Copy the new list on
-     to every machine on your network that has `send-pr' installed, and
-     make sure you advise remote submitters that the category list has
-     changed.  *Note Adding a problem category: mkcat.  Also *Note The
-     `categories' file: categories.
-
-*removing categories*
-     To remove a category, you need to make sure the relevant
-     subdirectory is empty (in other words, make sure no PRs exist for
-     the category you wish to remove).  You can then remove the
-     category listing from the `categories' file, and invoke
-
-          rmcat CATEGORY...
-
-     to remove CATEGORY (any number of categories may be specified on
-     the command line to `rmcat', so long as they abide by the above
-     constraints).
-
-     *Note*: this causes all category lists for `send-pr' (except the
-     one on the local machine) to become outdated.  Copy the new list on
-     to every machine on your network that has `send-pr' installed, and
-     make sure you advise remote submitters that the category list has
-     changed.  *Note Removing a problem category: rmcat.  Also *Note
-     The `categories' file: categories.
-
-*adding and removing maintainers*
-     Edit the `responsible' file to add a new maintainer or to remove an
-     existing maintainer.  *Note The `responsible' file: responsible.
-
-*building a distribution of `send-pr'*
-     You can build a distribution of `send-pr' which contains valid
-     information for your site by invoking the command `mkdist'.  *Note
-     Configuring `send-pr' for the outside world: mkdist.  You can then
-     distribute your customized `send-pr' to your customers, friends,
-     relatives, etc., so that they can submit Problem Reports to your
-     database.
-
-*building a new index*
-     If your index becomes corrupted, or if you wish to generate a new
-     one for some reason, use the program `gen-index' (*note
-     Regenerating the index: gen-index.).
-
-*pruning log files*
-     Log files often grow to unfathomable proportions.  As with
-     gardening, it is best to prune these as they grow, lest they take
-     over your disk and leave you with no room to gather more Problem
-     Reports.  If you keep log files, be sure to keep an eye on them.
-     (*Note Setting up mail aliases: Aliases.)
-
-*BACKING UP YOUR DATA*
-     Any database is only useful if its data remains uncorrupted and
-     safe.  Performing periodic backups ensures that problems like disk
-     crashes and data corruption are reversible.
-
-   *Note Where GNATS lives: Locations.
-
-* Menu:
-
-* Networked management::  Managing GNATS over a network
-* Local configuration::   Changing your local configuration
-* Admin files::           Administrative data files
-* Admin utils::           Administrative utilities
-* Internal utils::        Internal utilities
-
-
-File: gnats.info,  Node: Networked management,  Next: Local configuration,  Up: Management
-
-Managing GNATS over a network
-=============================
-
-   If you have installed the GNATS user tools on machines around your
-local network, there are a few things you need to remember.
-
-   `mkcat' and `rmcat' do not update the categories list for other
-machines on your network which have `send-pr' installed, unless those
-machines share PREFIX with the host machine).  To update these lists,
-copy the `send-pr' categories list to each of the other hosts.  This
-categories list is `PREFIX/lib/gnats/SITE', where SITE is the name tag
-for your local site, as specified in the `config' file as `GNATS_SITE'
-(*note The `config' file: config.).
-
-   It is also important to note that only your local `send-pr' has
-access to this new information; any copies of `send-pr' which you have
-distributed to outside submitters now have outdated category lists.
-You must either contact your submitters and instruct them to update
-their copy of the categories list, which they installed in
-`PREFIX/lib/gnats/SUPPORT-SITE' from the distribution you provided, or
-you must build another distribution of `send-pr' with this new
-information and redistribute it.
-
-   If you need to use GNATS utilities, like `query-pr' and `edit-pr',
-on other systems besides the one where GNATS itself resides, *note
-Installing the user tools: Installing tools..
-
-
-File: gnats.info,  Node: Local configuration,  Next: Admin files,  Prev: Networked management,  Up: Management
-
-Changing your local configuration
-=================================
-
-   *Note Where GNATS lives: Locations.
-
-   Your local configuration is determined by the data files in the
-directory `GNATS_ROOT/gnats-adm'.  These can be altered at any time by
-editing the pertinent file.
-
-`config'
-     Variables which control certain behavior.  *Note The `config'
-     file: config.  Behaviors you can change here include
-
-        * The address where your site receives Problem Reports.
-
-        * The address of the GNATS administrator.
-
-        * The nametag for your Support Site (your organization, company,
-          group, etc.).
-
-        * The nametag for your local Submitter Site.
-
-        * The default release for your site.
-
-        * The default value for the `>Organization:' field (this value
-          appears as the default when you run `send-pr').
-
-        * Whether or not to remind maintainers if a requisite time
-          period has passed before they change the state of a Problem
-          Report to `analyzed'.  (Also see *Note The `submitters' file:
-          submitters, and *Note Timely Reminders: at-pr.
-
-        * Whether or not to send an automatic acknowledgement to the
-          originator of a problem report when the GNATS first receives
-          the PR.
-
-        * The value GNATS assigns to PRs which come in with missing or
-          unknown values for the `>Submitter-Id:' field.
-
-        * Whether or not GNATS should retain `Received:' mail headers
-          from incoming mail.
-
-        * Whether or not GNATS is in a mode for debugging.
-
-        * The values which define business hours.
-
-`categories'
-     The list of categories that GNATS accepts as valid for the
-     `>Category:' field, and the maintainers responsible for each
-     category.  Update this file whenever you have a new category, or
-     whenever a category is no longer valid.  You must also update this
-     file whenever responsiblility for a category changes, or if a