Changes to gnats/doc/fields.texi

Yngve Svendsen <[email protected]> Tue, 22 Oct 2002 18:46:17 -0400
Newsgroups gmane.comp.bug-tracking.gnats.patches
Message-ID <[email protected]>
Index: gnats/doc/fields.texi
diff -c gnats/doc/fields.texi:1.4 gnats/doc/fields.texi:1.5
*** gnats/doc/fields.texi:1.4	Mon May 20 08:23:43 2002
--- gnats/doc/fields.texi	Tue Oct 22 18:46:17 2002
***************
*** 200,211 ****
  
  In a standard @sc{gnats} installation, certain fields will always be
  present in a Problem Report.  If a PR arrives without one or more of
! these fields, @sc{gnats} will add them, and if they have default values
! set by the configuration at the Support Site, they will be filled in
! with these values.  Certain tools such as @code{send-pr} are set up to
! provide sensible defaults for most fields.
! 
! (TODO: Make cross-reference to treatment of send-pr.conf)
  
  In the list below, the field type (@code{text}, @code{multitext},
  @code{enumerated}, etc.) is supplied in parantheses.  The different
--- 200,210 ----
  
  In a standard @sc{gnats} installation, certain fields will always be
  present in a Problem Report.  If a PR arrives without one or more of
! these fields, @sc{gnats} will add them, and if they have default
! values set by the configuration at the Support Site, they will be
! filled in with these values.  Certain tools such as @code{send-pr} are
! set up to provide sensible defaults for most fields
! (@pxref{send-pr.conf file,,The send-pr.conf configuration file}.)
  
  In the list below, the field type (@code{text}, @code{multitext},
  @code{enumerated}, etc.) is supplied in parantheses.  The different