From: Vladimir Panteleev <thecybershadow@gmail.com>
To: overseers@gcc.gnu.org
Subject: GCC bug reporting
Date: Fri, 05 Aug 2016 01:48:00 -0000 [thread overview]
Message-ID: <167ca182-d746-a9b7-4d72-aa46dd979354@gmail.com> (raw)
Hello,
I'd like to submit a GCC bug report.
https://gcc.gnu.org/bugs/ states the following:
> Please submit your bug report directly to the GCC bug tracker.
(link leads to https://gcc.gnu.org/bugzilla/)
However, account creation on https://gcc.gnu.org/bugzilla/ is disabled:
https://gcc.gnu.org/bugzilla/createaccount.cgi states the following:
> User account creation has been disabled.
> ----
> New accounts must be created by an administrator. The maintainer is
overseers@gcc.gnu.org.
Please advise.
next reply other threads:[~2016-08-05 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 1:48 Vladimir Panteleev [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-17 23:00 Keith Bennett
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=167ca182-d746-a9b7-4d72-aa46dd979354@gmail.com \
--to=thecybershadow@gmail.com \
--cc=overseers@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).