This is the mail archive of the gnats-devel@sources.redhat.com mailing list for the GNATS project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

[CORRECTED] Patch for typos in 3.113 gnats.texi


Original patch had the old and new files the wrong way round. Patches 
against 3.113 will be collected on sources.redhat.com in a few days.

Yngve Svendsen
IS Engineer
Clustra AS, Trondheim, Norway
yngve.svendsen@clustra.com
www.clustra.com


*** gnats-orig.texi     Mon Jan 15 18:05:59 2001
--- gnats.texi  Mon Jan 15 18:05:10 2001
***************
*** 114,120 ****
   * Management::            GNATS Administration
   * Installation::          Installing GNATS
   * Locations::             Where @sc{gnats} lives
! * Mulitple Databases::    Multiple @sc{gnats} databases on one host
   * Access Control::        Controlling access to @sc{gnats} databases
   * Regexps::               Querying using regular expressions
   * Index::
--- 114,120 ----
   * Management::            GNATS Administration
   * Installation::          Installing GNATS
   * Locations::             Where @sc{gnats} lives
! * Multiple Databases::    Multiple @sc{gnats} databases on one host
   * Access Control::        Controlling access to @sc{gnats} databases
   * Regexps::               Querying using regular expressions
   * Index::
***************
*** 164,170 ****

   @sc{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.  @sc{gnats} is a
   database specialized for a specific task.
--- 164,170 ----

   @sc{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 acknowledgment to
   the submitter that the report was received, and by making these Problem
   Reports accessible to queries and easily editable.  @sc{gnats} is a
   database specialized for a specific task.
***************
*** 200,206 ****

   @item
   Maintainers, managers and administrators can use @w{@code{query-pr}} to
! make inquiries about indidvidual PRs or groups of PRs.

   @end itemize

--- 200,206 ----

   @item
   Maintainers, managers and administrators can use @w{@code{query-pr}} to
! make inquiries about individual PRs or groups of PRs.

   @end itemize

***************
*** 233,239 ****

   Once a problem is recorded in the database, work can begin toward a
   solution.  A problem's initial @dfn{state} is @dfn{open}
! (@pxref{States,,States of Problem Reports}).  An acknowledgement is sent
   to the originator of the bug report (if that feature of @sc{gnats} is
   activated).  @sc{gnats} forwards copies of the report to the party
   responsible for that problem category and to the person responsible for
--- 233,239 ----

   Once a problem is recorded in the database, work can begin toward a
   solution.  A problem's initial @dfn{state} is @dfn{open}
! (@pxref{States,,States of Problem Reports}).  An acknowledgment is sent
   to the originator of the bug report (if that feature of @sc{gnats} is
   activated).  @sc{gnats} forwards copies of the report to the party
   responsible for that problem category and to the person responsible for
***************
*** 637,643 ****


   @c ===============================================================
! @node Mulitple Databases
   @appendix Multiple Databases on one host

   @sc{gnats} can support multiple databases on one host.  The options
--- 637,643 ----


   @c ===============================================================
! @node Multiple Databases
   @appendix Multiple Databases on one host

   @sc{gnats} can support multiple databases on one host.  The options
***************
*** 659,665 ****
   file.

   @example
! # list of GNATS databases and alaises
   #
   # Field 1 - fully qualified path to database
   # Field 2 - a comma separated list of aliases
--- 659,665 ----
   file.

   @example
! # list of GNATS databases and aliases
   #
   # Field 1 - fully qualified path to database
   # Field 2 - a comma separated list of aliases
***************
*** 709,715 ****
   @code{CHDB} command is allowed, and you just get one try.

   The second field of the @file{gnats-adm/gnatsd.conf} file is the access
! level for the user's host.  The default is @code{edit} to be compatable
   with previous releases of @code{gnats}.  If the user's hostname isn't in
   the @file{gnatsd.conf} file or its access level is @code{deny}, the
   connection is closed immediately.
--- 709,715 ----
   @code{CHDB} command is allowed, and you just get one try.

   The second field of the @file{gnats-adm/gnatsd.conf} file is the access
! level for the user's host.  The default is @code{edit} to be compatible
   with previous releases of @code{gnats}.  If the user's hostname isn't in
   the @file{gnatsd.conf} file or its access level is @code{deny}, the
   connection is closed immediately.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]