From: Craig Tenenbaum <zarathustra.zoroaster@gmail.com>
To: overseers@gcc.gnu.org
Subject: Account creation at GCC bugzilla
Date: Wed, 14 Jun 2017 19:49:00 -0000 [thread overview]
Message-ID: <CAGL-AsRMsmCtv-oLULTVnr-fxFxGs5_f7xoARwrJAQNVByi4og@mail.gmail.com> (raw)
Pursuant to an issue I raised on stack overflow:
https://stackoverflow.com/questions/44530264/safety-of-stdunordered-mapmerge,
and which was subsequently filed by proxy to the C++ LWG:
http://cplusplus.github.io/LWG/lwg-active.html#2977, I'd like to file
at least one bug against libstdc++, where I originally found the
issue. I'm fairly certain I've never created an account on gcc's
bugzilla and am informed that (understandably) automatic account
creation is currently disabled, and that I should make inquiries at
this address.
If there is a new protocol for reporting bugs than that listed on the
website, which indicates that I should file any new issues on the
bugzilla, I would appreciate any guidance that could be given. Thank
you so very much, sorry to have impinged on anyone's time.
reply other threads:[~2017-06-14 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGL-AsRMsmCtv-oLULTVnr-fxFxGs5_f7xoARwrJAQNVByi4og@mail.gmail.com \
--to=zarathustra.zoroaster@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).