In order to manage PRs, you need an account for our GNATS database
which is different from the authenticated access to the CVS repository
(though the username will be the same). If you do not have a GNATS
account yet (and think you should ;-)
) please contact
overseers@gcc.gnu.org.
Also, when you manage PRs, make sure mail-forwarding from gcc.gnu.org to your normal email account is activated; otherwise replies to status change notifications will bounce.
You can access the database either via gnatsweb, or via the gnatsd running on gcc.gnu.org.
Check out GNATS v3 from
:pserver:anoncvs@sources.redhat.com:/cvs/gnats
by means of
the -r gnats-v3-branch
option. Build and install that.
Add the the ../share/emacs/site-lisp/ directory installed by the GNATS
build to your load-path
in order to pick up the gnats library.
Finally, add the following entries to your .emacs
file
(load-library "gnats")
(setq gnats:network-server "gcc.gnu.org")
(setq gnats:userid "YourUserName")
(setq gnats:password "YourGNATSPassword")
(setq gnats:alias "gcc")
(autoload 'edit-pr "gnats"
"Command to edit a problem report." t)
(autoload 'query-pr "gnats"
"Command to query information about problem reports." t)
(If you already have PRMS support set up in you .emacs
file, remove that first, to avoid conflicts with duplicate symbols.)
To add a new report, you should be familiar with the general instructions. In addition, you might want to use the gccbug.el Emacs-Lisp file to aid putting forwarding bug reports from gcc-bugs into the gnats database.
As a GCC-specific convention, we will attach a special meaning to some fields. The State field should be used in the following way:
In addition, the high priority is reserved to maintainers in GCC, indicating that a certain problem must be solved before the next version of GCC is released.