public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/14402] New: gccbug confusion
Date: Wed, 03 Mar 2004 08:43:00 -0000 [thread overview]
Message-ID: <20040303084331.14402.wilson@gcc.gnu.org> (raw)
The http://gcc.gnu.org/bugs.html page says that use of gccbug will cause your
bug report to be mailed to the bug database, but this isn't true since we
switched from GNATS/PRMS to bugzilla. It just causes it to be mailed to
gcc-bugs where it then likely gets ignored.
Similarly, the BUGS file in release tar balls says the same thing.
gcc/doc/invoke.texi recommends use of gccbug, but should not.
gcc/doc/sourcebuild.texi also mentions gccbug, but it seems to be harmless.
Likewise for gcc/doc/configfiles.texi.
Perhaps we should get rid of gccbug?
--
Summary: gccbug confusion
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wilson at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14402
next reply other threads:[~2004-03-03 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:43 wilson at gcc dot gnu dot org [this message]
2004-03-03 10:40 ` [Bug other/14402] " jsm at polyomino dot org dot uk
2004-03-03 16:15 ` bangerth at dealii dot org
2004-03-03 16:22 ` pinskia at gcc dot gnu dot org
2004-03-03 19:08 ` wilson at specifixinc dot com
2004-03-04 1:36 ` dberlin at dberlin dot org
2004-03-04 21:16 ` wilson at gcc dot gnu dot org
2004-03-04 22:16 ` bangerth at dealii dot org
2004-04-27 19:17 ` pinskia at gcc dot gnu dot org
2005-02-07 6:58 ` cvs-commit at gcc dot gnu dot org
2005-02-07 10:40 ` pinskia at gcc dot gnu dot org
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=20040303084331.14402.wilson@gcc.gnu.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).