gnats-diffs
[Top][All Lists]
Advanced

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

Changes to gnats/doc/p-admin.texi


From: Yngve Svendsen
Subject: Changes to gnats/doc/p-admin.texi
Date: Sat, 26 Oct 2002 18:02:54 -0400

Index: gnats/doc/p-admin.texi
diff -c gnats/doc/p-admin.texi:1.28 gnats/doc/p-admin.texi:1.29
*** gnats/doc/p-admin.texi:1.28 Thu Oct 24 08:46:56 2002
--- gnats/doc/p-admin.texi      Sat Oct 26 18:02:53 2002
***************
*** 690,710 ****
  The @code{on-change} subsection of a @code{fields} section specifies one
  or more actions to be performed when the field value is edited by the
  user.  It has the general form
  @example
  on-change [ "query-expression" ] @{
- @*
  @ @ [ add-audit-trail ]
- @*
  @ @ [ audit-trail-format @{
  @ @ @ @ format "formatstring"
  @ @ @ @ [ fields @{ "fieldname" ... @} ]
  @ @ @} ]
- @*
  @ @ [ require-change-reason ]
- @*
  @ @ [ set-field | append-to-field "fieldname" @{
  @ @ @ @ "format-string" [ fieldlist ]
  @ @ @} ]
  @}
  @end example
  
--- 690,708 ----
  The @code{on-change} subsection of a @code{fields} section specifies one
  or more actions to be performed when the field value is edited by the
  user.  It has the general form
+ 
  @example
  on-change [ "query-expression" ] @{
  @ @ [ add-audit-trail ]
  @ @ [ audit-trail-format @{
  @ @ @ @ format "formatstring"
  @ @ @ @ [ fields @{ "fieldname" ... @} ]
  @ @ @} ]
  @ @ [ require-change-reason ]
  @ @ [ set-field | append-to-field "fieldname" @{
  @ @ @ @ "format-string" [ fieldlist ]
  @ @ @} ]
+ @ @ [ require @{ "fieldname" ... @} ]
  @}
  @end example
  
***************
*** 734,739 ****
--- 732,745 ----
  @code{append-to-field} option (the @code{read-only} option on a field is
  ignored).  However, the changes are subject to the usual field content
  checks.
+ 
+ The @code{require} option specifies that one or more fields must have
+ a (non-blank) value when this field is changed.
+ 
+ A field may be enforced to have a (non-blank) value at all times by
+ including it in the set of fields required for the initial PR, see
+ @ref{Initial PR input fields}, as well as in the set of fields
+ required on change of the field itself.
  
  There is also a global @code{on-change} section that is executed once
  for each PR edit.  A typical use for such a section is to set the




reply via email to

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