116 |
entries will also cause a copy of the new @samp{Audit-Trail} message to |
entries will also cause a copy of the new @samp{Audit-Trail} message to |
117 |
be sent. |
be sent. |
118 |
|
|
119 |
|
Mail received at the PR submission email address and recognized by |
120 |
|
@sc{gnats} as relating to an existing PR is also appended to the |
121 |
|
@samp{Audit-Trail} field, see @ref{follow-up via email}. |
122 |
|
|
123 |
@menu |
@menu |
124 |
* edit-pr from the shell:: Invoking @code{edit-pr} from the shell |
* edit-pr from the shell:: Invoking @code{edit-pr} from the shell |
125 |
|
* follow-up via email:: Following up via direct email |
126 |
@end menu |
@end menu |
127 |
|
|
128 |
@node edit-pr from the shell |
@node edit-pr from the shell |
190 |
standard input for a reason if you have changed a field that requires |
standard input for a reason if you have changed a field that requires |
191 |
specifying a reason for the change. |
specifying a reason for the change. |
192 |
|
|
193 |
|
@node follow-up via email |
194 |
|
@subsection Following up via direct email |
195 |
|
@cindex follow-up via email |
196 |
|
@cindex subsequent mail |
197 |
|
@cindex related mail |
198 |
|
|
199 |
|
If you have some additional information for a PR and for some reason |
200 |
|
do not want to (or cannot) edit the PR directly, you may append |
201 |
|
the information to the Audit-Trail field by mailing it to the PR |
202 |
|
submission address. |
203 |
|
|
204 |
|
In order for GNATS to be able to recognize the mail as pertaining to an |
205 |
|
existing PR (as opposed to a new PR, see @ref{Submitting via e-mail,,}), |
206 |
|
the Subject mail header field must contain a reference to the PR. |
207 |
|
GNATS matches the Subject header against the regular expression |
208 |
|
|
209 |
|
@smallexample |
210 |
|
\<(PR[ \t#/]?|[-\w+.]+/)[0-9]+ |
211 |
|
@end smallexample |
212 |
|
|
213 |
|
@noindent |
214 |
|
to determine whether such a reference is present. Any text may precede |
215 |
|
or follow the reference in the Subject header. If more than one reference |
216 |
|
is present, the first is used and the rest ignored. |
217 |
|
|
218 |
|
A PR reference matching the regular expression above has two parts. The |
219 |
|
second is the PR number (one or more digits). The first is either the |
220 |
|
capital letters 'PR' optionally followed by a separator character (blank, |
221 |
|
tab, hash mark or forward slash) or the category name followed by a |
222 |
|
forward slash. Following are some examples which match the regular |
223 |
|
expression: |
224 |
|
|
225 |
|
@smallexample |
226 |
|
PR 123 PR4567 PR#890 gnats/4711 |
227 |
|
@end smallexample |
228 |
|
|
229 |
|
The PR number and the category (if present) are checked for existence, |
230 |
|
and if the outcome is positive, the mail is appended to the Audit-Trail |
231 |
|
field of the PR. Note that the PR need not belong to the category because |
232 |
|
PRs may move between categories. |
233 |
|
|
234 |
|
Outgoing emails sent by GNATS itself may be configured to have a Subject |
235 |
|
header field that refers to the PR in question: |
236 |
|
|
237 |
|
@smallexample |
238 |
|
Subject: Re: PR @var{category}/@var{gnats-id}: @var{original message subject} |
239 |
|
@end smallexample |
240 |
|
|
241 |
|
This makes it extremely easy to follow up on a PR by replying to such an |
242 |
|
email, see @ref{dbconfig file,,The @code{dbconfig} file} and the sample, |
243 |
|
default @code{dbconfig} file installed by @code{mkdb}. |
244 |
|
|
245 |
@c --------------------------------------------------------------- |
@c --------------------------------------------------------------- |
246 |
@node query-pr |
@node query-pr |
247 |
@section Querying the database |
@section Querying the database |