public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: raz+tah.bet@raz.cx To: gcc-gnats@gcc.gnu.org Subject: web/8168: What is the preferred means of reporting bugs? Date: Tue, 08 Oct 2002 05:06:00 -0000 [thread overview] Message-ID: <20021008120404.22945.qmail@sources.redhat.com> (raw) >Number: 8168 >Category: web >Synopsis: What is the preferred means of reporting bugs? >Confidential: no >Severity: serious >Priority: medium >Responsible: gerald >State: open >Class: doc-bug >Submitter-Id: net >Arrival-Date: Tue Oct 08 05:06:03 PDT 2002 >Closed-Date: >Last-Modified: >Originator: raz+tah.bet@raz.cx >Release: unknown-1.0 >Organization: >Environment: >Description: Quoting from http://gcc.gnu.org/bugs.html > Please submit your bug report directly to the GCC > GNATS bug database. Only if this is not possible, > mail all information to bug-gcc@gnu.org or > gcc-bugs@gcc.gnu.org. Quoting from http://gcc.gnu.org/gnats.html (linked to "GCC GNATS bug database in above page) > The preferred way of submitting a bug report is by > means of the gccbug program that is automatically > installed with current versions of GCC and submits > the bug report by e-mail. > > If this is not possible, please use the gnatsweb > interface. Make sure you include an e-mail address, > so we can inform you when the status of your report > changes. So, the bugs page asks that the web interface be used in preference to the email interface while the web interface entry page asks that email be used. Did I miss something? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-08 12:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-08 5:06 raz+tah.bet [this message] 2002-10-08 11:26 Janis Johnson 2002-10-08 12:36 Janis Johnson 2002-10-08 15:06 Gerald Pfeifer 2002-12-20 21:18 bangerth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021008120404.22945.qmail@sources.redhat.com \ --to=raz+tah.bet@raz.cx \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).