From: Justin Vreeland <vreeland.justin@gmail.com>
To: overseers@gcc.gnu.org
Subject: gcc bugtracker
Date: Wed, 29 Oct 2014 13:37:00 -0000 [thread overview]
Message-ID: <CAA_T830-e6ybdxjvXSOCDr_9xt2ZrpmFsZX0J3Q4Qd2QKqtdjg@mail.gmail.com> (raw)
Hello,
I saw some posting in the mailing list asking people to help test out
and update some simple patches. I'd like to have access to the
bugzilla to update the relevant bugs and ask questions.
--Justin
reply other threads:[~2014-10-25 18:17 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=CAA_T830-e6ybdxjvXSOCDr_9xt2ZrpmFsZX0J3Q4Qd2QKqtdjg@mail.gmail.com \
--to=vreeland.justin@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).