gnats-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Changes to gnats/doc/gnats.texi


From: Yngve Svendsen
Subject: Changes to gnats/doc/gnats.texi
Date: Mon, 14 Oct 2002 18:11:59 -0400

Index: gnats/doc/gnats.texi
diff -c gnats/doc/gnats.texi:1.29 gnats/doc/gnats.texi:1.30
*** gnats/doc/gnats.texi:1.29   Mon Oct 14 16:36:50 2002
--- gnats/doc/gnats.texi        Mon Oct 14 18:11:58 2002
***************
*** 283,289 ****
  @sc{gnats} administrator (@pxref{Management,,@sc{gnats} Administration}).
  
  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 may be
  sent to the originator of the bug report (depending on whether this
  feature has been switched on in the @sc{gnats} configuration).
--- 283,289 ----
  @sc{gnats} administrator (@pxref{Management,,@sc{gnats} Administration}).
  
  Once a problem is recorded in the database, work can begin toward a
! solution.  A problem's initial @dfn{state} type is @dfn{open}
  (@pxref{States,,States of Problem Reports}).  An acknowledgment may be
  sent to the originator of the bug report (depending on whether this
  feature has been switched on in the @sc{gnats} configuration).
***************
*** 312,318 ****
  It should be emphasized that what we describe here is the default way
  that @sc{gnats} works, but as of version 4, @sc{gnats} is extremely
  customizable, allowing sites to tailor almost every aspect of its
! behavior.  @xref{dbconfig file,,The @code{dbconfig} file}.
  
  @node Flowchart
  @section Flowchart of @sc{gnats} activities
--- 312,319 ----
  It should be emphasized that what we describe here is the default way
  that @sc{gnats} works, but as of version 4, @sc{gnats} is extremely
  customizable, allowing sites to tailor almost every aspect of its
! behavior.  See for instance @ref{dbconfig file,,The @code{dbconfig}
! file} and @xref{States,,States of Problem Reports}).
  
  @node Flowchart
  @section Flowchart of @sc{gnats} activities
***************
*** 1868,1878 ****
  @end smallexample
  
  @noindent
! in this case, since the only value for @samp{>State:} which matches the
! expression @samp{o} is @samp{open}.  @samp{State="o"} also matches
! @samp{o}, @samp{oswald}, and even @samp{oooooo}, but none of those
! values are valid states for a Problem Report in default @sc{gnats}
! installations.
  
  We can also use the expression operator @samp{|} to signify a logical
  @code{OR}, such that
--- 1869,1879 ----
  @end smallexample
  
  @noindent
! in this case, since the only value for @samp{>State:} which matches
! the expression @samp{o} in a standard installation is @samp{open}.
! @samp{State="o"} also matches @samp{o}, @samp{oswald}, and even
! @samp{oooooo}, but none of those values are valid states for a Problem
! Report in default @sc{gnats} installations.
  
  We can also use the expression operator @samp{|} to signify a logical
  @code{OR}, such that




reply via email to

[Prev in Thread] Current Thread [Next in Thread]