From: "Casper Ti. Vector" <caspervector@gmail.com>
To: overseers@gcc.gnu.org
Subject: Request for registration on GCC bugzilla
Date: Tue, 28 Feb 2017 10:35:00 -0000 [thread overview]
Message-ID: <20170228103522.GA5847@CasperVector> (raw)
As the title; for the bug I would like to report, please see
<https://gcc.gnu.org/ml/gcc-bugs/2017-02/msg03275.html>.
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
reply other threads:[~2017-02-28 10:35 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=20170228103522.GA5847@CasperVector \
--to=caspervector@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).