[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to gnats/doc/p-admin.texi
From: |
Andrew J. Gray |
Subject: |
Changes to gnats/doc/p-admin.texi |
Date: |
Thu, 24 Oct 2002 08:46:57 -0400 |
Index: gnats/doc/p-admin.texi
diff -c gnats/doc/p-admin.texi:1.27 gnats/doc/p-admin.texi:1.28
*** gnats/doc/p-admin.texi:1.27 Mon Oct 14 18:11:58 2002
--- gnats/doc/p-admin.texi Thu Oct 24 08:46:56 2002
***************
*** 1069,1080 ****
An @code{initial-entry} section in the @file{dbconfig} file is used to
describe which fields should be present on initial PR entry; this is
used by tools such as send-pr to determine which fields to include in a
! ``blank'' PR template. The general format for the @code{initial-entry}
! section is
@example
initial-entry @{
@ @ fields @{ "fieldname" [ "fieldname" ... ] @}
@}
@end example
--- 1069,1084 ----
An @code{initial-entry} section in the @file{dbconfig} file is used to
describe which fields should be present on initial PR entry; this is
used by tools such as send-pr to determine which fields to include in a
! ``blank'' PR template. An optional @code{require} parameter can be
! defined to specify a subset of the @code{intial-entry} fields which must
! be assigned a value upon initial creation of the PR.
!
! The general format for the @code{initial-entry} section is
@example
initial-entry @{
@ @ fields @{ "fieldname" [ "fieldname" ... ] @}
+ @ @ [ require @{ "fieldname" [ "fieldname" ... ] @} ]
@}
@end example