196 |
|
|
197 |
@c FIXME - this node is loooooooooooooooong... |
@c FIXME - this node is loooooooooooooooong... |
198 |
|
|
|
@subheading Field descriptions |
|
|
|
|
199 |
In a standard @sc{gnats} installation, certain fields will always be |
In a standard @sc{gnats} installation, certain fields will always be |
200 |
present in a Problem Report. If a PR arrives without one or more of |
present in a Problem Report. If a PR arrives without one or more of |
201 |
these fields, @sc{gnats} will add them, and if they have default |
these fields, @sc{gnats} will add them, and if they have default |
501 |
The reason for the change. |
The reason for the change. |
502 |
@end table |
@end table |
503 |
|
|
504 |
|
@cindex follow-up via email |
505 |
@cindex subsequent mail |
@cindex subsequent mail |
|
@cindex other mail |
|
|
@cindex appending PRs |
|
|
@cindex saving related mail |
|
506 |
@cindex related mail |
@cindex related mail |
507 |
@noindent |
@noindent |
508 |
The @code{Audit-Trail} field also contains any mail messages received by |
The @code{Audit-Trail} field also contains any mail messages received by |
509 |
@sc{gnats} related to this PR, in the order received. @sc{gnats} needs |
@sc{gnats} related to this PR, in the order received. @sc{gnats} needs |
510 |
to find a @var{category}/@var{number} at the beginning of the Subject |
to find a reference to the PR in the Subject field of received email in |
511 |
field of received e-mail in order to be able to file it correctly. |
order to be able to file it correctly, see @ref{follow-up via email,, |
512 |
|
Following up via direct email}. |
513 |
|
|
514 |
@cindex @code{Unformatted} field |
@cindex @code{Unformatted} field |
515 |
@item Unformatted |
@item Unformatted |