From: Joern Rennecke <joern.rennecke@embecosm.com>
To: overseers@sourceware.org
Subject: gcc bugzilla
Date: Thu, 30 Nov 2023 05:14:04 +0000 [thread overview]
Message-ID: <CAMqJFCqWgN8APw-NmPLpu4=HPU4i78wiB1zAArVYmxiWm9Zm-g@mail.gmail.com> (raw)
When I try to go to https://gcc.gnu.org/bugzilla/ (e.g. following the
bug data base link from the gcc .homepage), I get web page with an
error message:
Software error:
Can't connect to the database.
Error: Too many connections
Is your database installed and up and running?
Do you have the correct username and password selected in localconfig?
For help, please send mail to the webmaster (root@localhost), giving
this error message and the time and date of the error.
next reply other threads:[~2023-11-30 5:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 5:14 Joern Rennecke [this message]
2023-11-30 8:12 ` gcc bugzilla (and patchwork) Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2017-03-30 10:20 GCC Bugzilla Alfred Agrell
2017-03-12 9:46 GCC bugzilla joris
2016-10-07 15:37 nicolas bouillot
2010-10-28 21:31 GCC Bugzilla Paul Koning
2010-10-28 21:38 ` Andrew Pinski
2010-10-29 0:31 ` Paul Koning
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='CAMqJFCqWgN8APw-NmPLpu4=HPU4i78wiB1zAArVYmxiWm9Zm-g@mail.gmail.com' \
--to=joern.rennecke@embecosm.com \
--cc=overseers@sourceware.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).