A Problem Report is a message that describes a problem you are
having with a body of work. send-pr organizes this message into
a form which can be understood and automatically processed by GNATS,
the GNU Problem Report Management System. A Problem Report is
organized into fields which contain data describing you, your
organization, and the problem you are announcing (see section Problem Report format). Problem Reports go through several defined states in
their lifetimes, from open to closed (see section States of Problem Reports).
Each PR goes through a defined series of states between origination and closure. The originator of a PR receives notification automatically of any state changes.
The format of a PR is designed to reflect the nature of GNATS as a database. Information is arranged into fields, and kept in individual records (Problem Reports).
Problem Report fields are denoted by a keyword which begins with `>' and ends with `:', as in `>Confidential:'. Fields belong to one of three data types:
send-pr template as a comment.
The following fields are ENUMERATED format; see the descriptions of
fields below for explanations of each field in detail:
>Confidential: >Severity: >Priority: >Class: >State: >Number:
>Submitter-Id: >Originator: >Synopsis: >Category: >Release: >Responsible: >Arrival-Date:
>Organization: >Environment: >Description: >How-To-Repeat: >Fix: >Audit-Trail: >Unformatted:
A Problem Report contains two different types of fields: Mail Header fields, which are used by the mail handler for delivery, and Problem Report fields, which contain information relevant to the Problem Report and its submitter. A Problem Report is essentially a specially formatted electronic mail message.
The following is an example Problem Report. Mail headers are at the top, followed by GNATS fields, which begin with `>' and end with `:'. The `Subject:' line in the mail header and the `>Synopsis:' field are usually duplicates of each other.
Message-Id: message-id Date: date From: address Reply-To: address To: bug-address Subject: subject >Number: gnats-id >Category: category >Synopsis: synopsis >Confidential: yes or no >Severity: critical, serious, or non-critical >Priority: high, medium or low >Responsible: responsible >State: open, analyzed, suspended, feedback, or closed >Class: sw-bug, doc-bug, change-request, support, or duplicate >Submitter-Id: submitter-id >Arrival-Date: date >Originator: name >Organization: organization >Release: release >Environment: environment >Description: description >How-To-Repeat: how-to-repeat >Fix: fix >Audit-Trail: appended-messages... State-Changed-From-To: from-to State-Changed-When: date State-Changed-Why: reason Responsible-Changed-From-To: from-to Responsible-Changed-When: date Responsible-Changed-Why: reason >Unformatted: miscellaneous
A Problem Report may contain any mail header field described in the
Internet standard RFC-822. However, only the fields which identify the
sender and the subject are required by send-pr:
To:
send-pr.
Subject:
From:
Reply-To:
From: field.
The following fields are present whenever a PR is submitted via the
program send-pr. GNATS adds additional fields when the PR
arrives at the Support Site; explanations of these follow this list.
>Submitter-Id:
send-pr with the `--request-id' option to apply for one from
the support organization. Problem Reports from those not affiliated
with the support organization should use the default value of `net'
for this field.)
>Originator:
NAME.
>Organization:
DEFAULT_ORGANIZATION in the
send-pr shell script.
>Confidential:
>Synopsis:
send-pr copies
this information to the `Subject:' line when you submit a Problem
Report.
>Severity:
critical
serious
non-critical
>Priority:
high
medium
low
>Category:
>Class:
sw-bug
doc-bug
change-request
support
duplicate (pr-number)
>Release:
>Environment:
>Description:
>How-To-Repeat:
>Fix:
GNATS adds the following fields when the PR arrives at the Support Site:
>Number:
category/numberin subsequent email messages. This is for historical reasons, as well as because Problem Reports are stored in subdirectories which are named by category.
>State:
open
analyzed
feedback
closed
suspended
>Responsible:
>Arrival-Date:
>Audit-Trail:
State-Changed-<From>-<To>: oldstate>-<newstate
Responsible-Changed-<From>-<To>: oldresp>-<newresp
State-Changed-By: name
Responsible-Changed-By: name
State-Changed-When: timestamp
Responsible-Changed-When: timestamp
State-Changed-Why: reason...
Responsible-Changed-Why: reason...
>Unformatted:
You can invoke send-pr from a shell prompt or from within
GNU Emacs using `M-x send-pr'.
Invoking send-pr presents a PR template with a number of
fields already filled in. Complete the template as thoroughly as
possible to make a useful bug report. Submit only one bug with each PR.
A template consists of three sections:
send-pr creates a standard mail header. send-pr completes
all fields except the `Subject:' line with default values.
(See section Problem Report format.)
For examples of a Problem Report template and complete Problem Report, see section An Example.
The default template contains your preconfigured `>Submitter-Id:'.
send-pr attempts to determine values for the `>Originator:'
and `>Organization:' fields (see section Problem Report format). send-pr also attempts to find out some information
about your system and architecture, and places this information in the
`>Environment:' field if it finds any.
You may submit problem reports to different Support Sites from the
default site by specifying the alternate site when you invoke
send-pr. Each site has its own list of categories for
which it accepts Problem Reports.
(See section Setting a default site.)
send-pr also provides the mail header section of the template
with default values in the `To:', `From:', and
`Reply-To:' fields. The `Subject:' field is empty.
The template begins with a comment section:
SEND-PR: -*- send-pr -*- SEND-PR: Lines starting with `SEND-PR' will be removed SEND-PR: automatically as well as all comments (the text SEND-PR: below enclosed in `<' and `>'). SEND-PR: SEND-PR: Please consult the document `Reporting Problems SEND-PR: Using send-pr' if you are not sure how to fill out SEND-PR: a problem report. SEND-PR: SEND-PR: Choose from the following categories:
and also contains a list of valid >Category: values for the
Support Site to whom you are submitting this Problem Report. One (and
only one) of these values should be placed in the >Category:
field.
A complete sample bug report, from template to completed PR, is shown in
section An Example. For a complete list of valid categories, type
`send-pr -L' at your prompt. See section Valid Categories, for a sample list of categories, .
The mail header is just below the comment section. Fill out the `Subject:' field, if it is not already completed using the value of `>Synopsis:'. The other mail header fields contain default values.
To: support-site Subject: complete this field From: your-login@your-site Reply-To: your-login@your-site X-send-pr-version: send-pr 3.2
where support-site is an alias for the Support Site you wish to submit this PR to.
The rest of the template contains GNATS fields. Each field is either automatically completed with valid information (such as your `>Submitter-Id:') or contains a one-line instruction specifying the information that field requires in order to be correct. For example, the `>Confidential:' field expects a value of `yes' or `no', and the answer must fit on one line; similarly, the `>Synopsis:' field expects a short synopsis of the problem, which must also fit on one line. Fill out the fields as completely as possible. See section Helpful hints, for suggestions as to what kinds of information to include.
In this example, words in italics are filled in with pre-configured information:
>Submitter-Id: your submitter-id
>Originator: your name here
>Organization:
your organization
>Confidential:<[ yes | no ] (one line)>
>Synopsis: <synopsis of the problem (one line)>
>Severity: <[non-critical | serious | critical](one line)>
>Priority: <[ low | medium | high ] (one line)>
>Category: <name of the product (one line)>
>Class: <[sw-bug | doc-bug | change-request | support]>
>Release: <release number or tag (one line)>
>Environment:
<machine, os, target, libraries (multiple lines)>
>Description:
<precise description of the problem (multiple lines)>
>How-To-Repeat:
<code/input/activities to reproduce (multiple lines)>
>Fix:
<how to correct or work around the problem, if known
(multiple lines)>
When you finish editing the Problem Report, send-pr mails it to
the address named in the `To:' field in the mail header.
send-pr checks that the complete form contains a valid
`>Category:'.
Your copy of send-pr should have already been customized on
installation to reflect your `>Submitter-Id:'. (See section Installing send-pr on your system.) If you don't
know your `>Submitter-Id:', you can request it using
`send-pr --request-id'. If your organization is not affiliated
with the site you send Problem Reports to, a good generic
`>Submitter-Id:' to use is `net'.
If your PR has an invalid value in one of the ENUMERATED fields
(see section Problem Report format), send-pr places the PR in
a temporary file named `/tmp/pbadnnnn' on your machine.
nnnn is the process identification number given to your current
send-pr session. If you are running send-pr from the
shell, you are prompted as to whether or not you wish to try editing the
same Problem Report again. If you are running send-pr from
Emacs, the Problem Report is placed in the buffer
`*send-pr-error*'; you can edit this file and then submit it
with
M-x gnats-submit-pr
Any further mail concerning this Problem Report should be carbon-copied to the GNATS mailing address as well, with the category and identification number in the `Subject:' line of the message.
Subject: Re: PR category/gnats-id: original message subject
Messages which arrive with `Subject:' lines of this form are automatically appended to the Problem Report in the `>Audit-Trail:' field in the order received.
send-pr from within Emacs
You can use an interactive send-pr interface from within GNU
Emacs to fill out your Problem Report. We recommend that you
familiarize yourself with Emacs before using this feature
(see section `Introduction' in GNU Emacs).
Call send-pr with `M-x send-pr'.(1) send-pr responds with a
Problem Report template preconfigured for the Support Site from which
you received send-pr. (If you use send-pr locally, the
default Support Site is probably your local site.)
You may also submit problem reports to different Support Sites from the
default site. To use this feature, invoke send-pr with
C-u M-x send-pr
send-pr prompts you for the name of a site. site is
an alias on your local machine which points to an alternate Support
Site.
send-pr displays the template and prompts you in the minibuffer
with the line:
>Category: other
Delete the default value `other' in the minibuffer and
replace it with the keyword corresponding to your problem (the list of
valid categories is in the topmost section of the PR template). For
example, if the problem you wish to report has to do with the GNU C
compiler, and your support organization accepts bugs submitted for this
program under the category `gcc', delete `other' and then type
`gcc[RET]'. send-pr replaces the line
>Category: <name of the product (one line)>
in the template with
>Category: gcc
and moves on to another field.
send-pr provides name completion in the minibuffer. For
instance, you can also type `gc[TAB]', and send-pr
attempts to complete the entry for you. Typing `g[TAB]'
may not have the same effect if several possible entries begin with
`g'. In that case send-pr cannot complete the entry because
it cannot determine whether you mean `gcc' or, for example,
`gdb', if both of those are possible categories.
send-pr continues to prompt you for a valid entry until you
enter one.
send-pr prompts you interactively to enter each field for
which there is a range of specific choices. If you attempt to enter a
value which is not in the range of acceptable entries, send-pr
responds with `[No match]' and allows you to change the entry
until it contains an acceptable value. This avoids unusable information
(at least in these fields) and also avoids typographical errors which
could cause problems later.
send-pr prompts you for the following fields:
>Category:
>Confidential: (default: no)
>Severity: (default: serious)
>Priority: (default: medium)
>Class: (default: sw-bug)
>Release:
>Synopsis: (this value is copied to Subject:)
After you complete these fields, send-pr places the cursor in
the `>Description:' field and displays the message
To send the problem report use: C-c C-c
in the minibuffer. At this point, edit the file in the main buffer to reflect your specific problem, putting relevant information in the proper fields. See section An Example, for a sample Problem Report.
`send-pr' provides a few key bindings to make moving around in a template buffer more simple:
C-c C-f
M-x change-field
edit-pr prompts you for a
new value.
M-C-b
M-x gnats-backward-field
M-C-f
M-x gnats-forward-field
M-p
M-x gnats-previous-field
M-n
M-x gnats-next-field
send-pr takes over again when you type `C-c C-c' to send the
message. send-pr reports any errors in a separate buffer, which
remains in existence until you send the PR properly (or, of course,
until you explicitly kill the buffer).
For detailed instructions on using Emacs, see section `Introduction' in GNU Emacs.
send-pr from the shell
send-pr [ site ]
[ -f problem-report | --file problem-report ]
[ -t mail-address | --to mail-address ]
[ --request-id ]
[ -L | --list ] [ -P | --print ]
[ -V | --version] [ -h | --help ]
site is an alias on your local machine which points to an address
used by a Support Site. If this argument is not present, the default
site is usually the site which you received send-pr from,
or your local site if you use GNATS locally.
(See section Setting a default site.)
Invoking send-pr with no options calls the editor named in your
environment variable EDITOR on a default PR template. If the
environment variable PR_FORM is set, its value is used as a file
name which contains a valid template. If PR_FORM points to a
missing or unreadable file, or if the file is empty, send-pr
generates an error message and opens the editor on a default template.
-f problem-report
--file problem-report
send-pr sends the contents of the file without
invoking an editor. If problem-report is `-',
send-pr reads from standard input.
-t mail-address
--to mail-address
send-pr is configured. This option is not recommended;
instead, use the argument site on the command line.
--request-id
>Submitter-Id: to the Support Site.
-L
--list
>Category: values on standard output.
No mail is sent.
-P
--print
PR_FORM is set in your
environment, the file it specifies is printed. If PR_FORM is not
set, send-pr prints the standard blank form. If the file
specified by PR_FORM doesn't exist, send-pr displays an
error message. No mail is sent.
-V
--version
send-pr version number and a usage summary. No mail
is sent.
-h
--help
send-pr. No mail is sent.
There is no orthodox standard for submitting effective bug reports,
though you might do well to consult the section on submitting bugs for
GNU gcc in section `Reporting Bugs' in Using and Porting GNU CC, by Richard Stallman. This section contains
instructions on what kinds of information to include and what kinds of
mistakes to avoid.
In general, common sense (assuming such an animal exists) dictates the kind of information that would be most helpful in tracking down and resolving problems in software.
Cygnus Support in Mountain View, CA, uses GNATS and send-pr
extensively for their support activities. As a support company, Cygnus
finds problem tracking to be a crucial part of everyday business.
Cygnus supports the GNU compiling tools (including GNATS and
send-pr) over several many platforms
With each shipment of the Cygnus Support Developer's Kit, customers
receive the latest version of send-pr, which contains an
up-to-date listing of valid categories (values for the >Category:
field). Using these tools, Cygnus' customers can communicate their
problems to Cygnus effectively and receive automatic confirmation of
receipt as well as notification of changes in the status of their
reported problems. Much of Cygnus' support mechanism relies on
electronic mail.
As an example, let's pretend we're a customer of Cygnus Support, and that we're having a problem compiling some of our software using the GNU C compiler, which Cygnus supports.
Assume that we're getting an error in our bifrabulator program
wherein the `prestidigitation' routines don't match with the
`whatsitsname'. We've made sure we're following the rules of the
program and checked the Release Notes from Cygnus and found that the bug
isn't already known. In other words, we're pretty sure we've found a
bug.
Our first step is to call send-pr. It really doesn't matter
whether we use send-pr from the shell or from within Emacs.
Indeed, if we use Emacs as a primary editor, calling send-pr from
the shell is likely to start send-pr in an Emacs buffer anyway.
So, since our company, Imaginary Software, Ltd., uses GNU
software extensively, we're pretty familiar with Emacs, so from within
Emacs we type
M-x send-prand we're greeted with the following screen:
SEND-PR: -*- text -*-
SEND-PR: Lines starting with `SEND-PR' will be removed
SEND-PR: automatically as well as all comments (the text
SEND-PR: below enclosed in `<' and `>').
SEND-PR: Please consult the manual if you are not sure
SEND-PR: how to fill out a problem report.
SEND-PR:
SEND-PR: Choose from the following categories:
SEND-PR:
SEND-PR: bfd binutils bison
SEND-PR: byacc clib config cvs diff
SEND-PR: doc emacs flex g++ gas
SEND-PR: gcc gdb glob gprof grep
SEND-PR: info ispell kerberos ld libg++
SEND-PR: libiberty make makeinfo mas newlib
SEND-PR: other patch rcs readline send-pr
SEND-PR: test texindex texinfo texinfo.tex
SEND-PR: bifrabulator <---note: this one is fake
SEND-PR:
To: cygnus-bugs@cygnus.com
Subject:
From: jeffrey@imaginary.com
Reply-To: jeffrey@imaginary.com
X-send-pr-version: send-pr 3.2
>Submitter-Id: imaginary
>Originator: Jeffrey Osier
>Organization:
Imaginary Software, Ltd.
>Confidential: <[ yes | no ] (one line)>
>Synopsis: <synopsis of the problem (one line)>
>Severity: <[ non-critical | serious | critical ] (one line)>
>Priority: <[ low | medium | high ] (one line)>
>Category: <name of the product (one line)>
>Class: <[sw-bug|doc-bug|change-request|support](oneline)>
>Release: <release number or tag (one line)>
>Environment:
<machine, os, target, libraries (multiple lines)>
System: SunOS imaginary.com 4.1.1 1 sun4
Architecture: sun4
>Description:
<precise description of the problem (multiple lines)>
>How-To-Repeat:
<code/input/activities to reproduce (multiple lines)>
>Fix:
@hrule
-----Emacs: *send-pr* (send-pr Fill)----All------------------
@hrule
>Category: other[]
We know from past experience that we need to set certain information into
each field, so we compile all the information we know about our problem.
We have some sample code which we know should work, even though it
doesn't, so we'll include that. Below is the completed PR; we send this
using C-c C-c. (The comments have been truncated).
SEND-PR: Lines starting with `SEND-PR' will be removed SEND-PR: automatically as well as all comments (the text SEND-PR: ... SEND-PR: To: cygnus-bugs@cygnus.com Subject: bifrabulator routines don't match From: jeffrey@imaginary.com Reply-To: jeffrey@imaginary.com X-send-pr-version: send-pr 3.2 >Submitter-Id: imaginary >Originator: Jeffrey Osier >Organization: Imaginary Software, Ltd. >Confidential: no >Synopsis: bifrabulator routines don't match >Severity: serious >Priority: medium >Category: bifrabulator >Class: sw-bug >Release: progressive-930101 >Environment: System: SunOS imaginary.com 4.1.1 1 sun4 Architecture: sun4 (SPARC) >Description: the following code I fed into the bifrabulator came back with a strange error. apparently, the prestidigitation routine doesn't match with the whatsitsname in all cases. >How-To-Repeat: call the bifrabulator on the following code. code sample... >Fix: @hrule -----Emacs: *send-pr* (send-pr Fill)----All------------------ @hrule To send the problem report use: C-c C-c
We type C-c C-c, and off it goes. Now, we depend on Cygnus Support to figure out the answer to our problem.
Soon afterward, we get the following message from Cygnus:
From: gnats (GNATS management) Sender: gnats-admin Reply-To: hacker@cygnus.com To: jeffrey@imaginary.com Subject: Re: bifrabulator/1425: routines don't match Thank you very much for your problem report. It has the internal identification: g++/1425. The individual assigned to look at your bug is: hacker (F.B. Hacker) Category: bifrabulator Responsible: hacker Synopsis: bifrabulator routines don't match Arrival-Date: Sat Feb 30 03:12:55 1993
This is our receipt that the bug has been accepted and forwarded to the responsible party.
A while later, we get the analysis:
To: jeffrey@imaginary.com From: hacker@cygnus.com Subject: Re: bifrabulator/1425: routines don't match Reply-To: hacker@cygnus.com Got your message, Jeff. It seems that the bifrabulator was confusing the prestidigitation routines with the realitychecker when lexically parsing the whatsitsname. I'm working on robustisizing the bifrabulator now. How about lunch next week? -- F.B. Hacker Cygnus Support, Mountain View, CA 415 903 1400 #include <std-disclaimer.h>
About the same time, we get another message from Cygnus.
From: hacker@cygnus.com
To: jeffrey@imaginary.com
Subject: Re: bifrabulator/1425: doesn't match prestidig
Reply-To: hacker@cygnus.com
`F.B. Hacker' changed the state to `analyzed'.
State-Changed-From-To: open-analyzed
State-Changed-By: hacker
State-Changed-When: Fri Feb 31 1993 08:59:16 1993
State-Changed-Why:
figured out the problem, working on a patch this afternoon
--
F.B. Hacker
Cygnus Support, Mountain View, CA 415 903 1400
#include <std-disclaimer.h>
The bug has now been analyzed, and Cygnus is working on a solution.
Sometime later, we get more mail from F.B.:
To: jeffrey@imaginary.com From: hacker@cygnus.com Subject: Re: bifrabulator/1425: routines don't match Reply-To: hacker@cygnus.com There's a patch now that you can ftp over and check out. Hey, that joke you sent me was great! The one about the strings walking into a bar... my boss laughed for an hour! -- F.B. Hacker Cygnus Support, Mountain View, CA 415 903 1400 #include <std-disclaimer.h>
From: hacker@cygnus.com
To: jeffrey@imaginary.com
Subject: Re: bifrabulator/1425: doesn't match prestidig
Reply-To: hacker@cygnus.com
`F.B. Hacker' changed the state to `feedback'.
State-Changed-From-To: analyzed-feedback
State-Changed-By: hacker
State-Changed-When: Fri Feb 31 1993 23:43:16 1993
State-Changed-Why:
got the patch finished, notified Jeff at Imaginary Software
--
F.B. Hacker
Cygnus Support, Mountain View, CA 415 903 1400
#include <std-disclaimer.h>
The bug has gone into feedback status now, until we get the patch, install it and test it. When everything tests well, we can mail F.B. back and tell him the bug's been fixed, and he can change the state of the PR from feedback to closed.
Following is a list of valid `>Category:' entries that are supported by Cygnus.
bfd
bifrabulator
binutils
ar, nm, size...).
bison
byacc
config
cvs
diff
diff program.
doc
emacs
flex
g++
gas
gcc
gdb
glob
gprof
grep
grep program.
info
info hypertext reader.
ispell
kerberos
ld
libc
libg++
libiberty
libm
make
make program.
makeinfo
mas
newlib
patch
gnats
rcs
readline
readline library.
send-pr
test
send-pr.
texindex
texinfo
other
send-pr on your system
If you receive send-pr as part of a larger software distribution,
it probably gets installed when the full distribution is installed. If
you are using GNATS at your site as well, you must decide where
send-pr sends Problem Reports by default; see section Setting a default site.
send-pr by itself
Install send-pr by following these steps (you may need
root access in order to change the `aliases' file and to
install send-pr):
make all install [ info ] [ install-info ] [ clean ]The targets mean the following:
all
send-pr and install-sid
install
install-sid
send-pr
send-pr.1
site
send-pr, installed as
`prefix/lib/gnats/site'
send-pr.el
info (optional)
install-info (optional)
clean (optional)
install-sid your-sidwhere your-sid is the identification code you received with
send-pr. send-pr automatically inserts this value
into the template field `>Submitter-Id:'. If you've downloaded
send-pr from the Net, use `net' for this value.
(autoload 'send-pr "send-pr" "Submit a Problem Report." t)
send-pr, and for every site with which you wish to use
send-pr to communicate. Each alias must have a suffix of
`-gnats'. The Support Site(s) will provide the correct addresses
where these aliases should point. For instance, edit your mail aliases
file to contain something like:
# support sites; for use with send-pr cygnus-gnats: bugs@cygnus.com # Cygnus Support bumblebee-gnats: bumblebugs@bumblebee.com # Bumblebee Inc. mycompany-gnats: bugs@my.company.com (if you use GNATS locally)
send-pr automatically searches for these aliases when you type
send-pr cygnus send-pr bumblebee send-pr site...
send-pr also uses site to determine the categories of
problems accepted by the site in question by looking in
prefix/lib/gnats/site
send-pr is capable of sending Problem Reports to any number of
Support Sites, using mail aliases which have `-gnats' appended them.
send-pr automatically appends the suffix, so that when you type
send-pr site
the Problem Report goes to the address noted in the `aliases' file
as `site-gnats'. You can do this in the Emacs version of
send-pr by invoking the program with
C-u M-x send-pr
You are prompted for site.
site is also used to error-check the `>Category:' field, as a precaution against sending mistaken information (and against sending information to the wrong site).
You may also simply type
send-pr
from the shell (or `M-x send-pr' in Emacs), and the Problem
Report you generate will be sent to the site, which is usually the
site from which you received your distribution of send-pr.
If you use GNATS at your own organization, the default is usually
your local address for reporting problems.
To change this, simply edit the file `Makefile' before installing and change the line
GNATS_SITE = site
to reflect the site where you wish to send PRs by default.
>Arrival-Date:
>Audit-Trail:
>Category:
>Class:
>Confidential:
>Description:
>Environment:
>Fix:
>How-To-Repeat:
>Number:
>Organization:
>Originator:
>Priority:
>Release:
>Responsible:
>Severity:
>State:
>Submitter-Id:
>Synopsis:
>Unformatted:
Arrival-Date field
Audit-Trail field
bifrabulator
Category field
Class field
Confidential field
Description field
send-pr
Environment field
Fix field
From: header
How-To-Repeat field
send-pr from Emacs
send-pr from the shell
Number field
Organization field
Originator field
Priority field
Release field
Reply-To: header
Responsible field
Responsible-Changed-<From>-<To>: in >Audit-Trail:
Responsible-Changed-By: in >Audit-Trail:
Responsible-Changed-When: in >Audit-Trail:
Responsible-Changed-Why: in >Audit-Trail:
send-pr fields
send-pr within Emacs
Severity field
State field
State-Changed-<From>-<To>: in >Audit-Trail:
State-Changed-By: in >Audit-Trail:
State-Changed-When: in >Audit-Trail:
State-Changed-Why: in >Audit-Trail:
Subject: header
Submitter-Id field
Synopsis field
To: header
Unformatted field
send-pr from within Emacs