From: nick <xerofoify@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Cc: Richard Biener <rguenther@suse.de>, Martin Sebor <msebor@gmail.com>
Subject: GSOC initial Draft
Date: Wed, 27 Mar 2019 22:14:00 -0000 [thread overview]
Message-ID: <30e46a16-5801-e787-30e9-c7c68a0dab8b@gmail.com> (raw)
Greetings All,
Sorry about another message but seems it was better to write an initial draft
for review here:
https://docs.google.com/document/d/1BKVeh62IpigsQYf_fJqkdu_js0EeGdKtXInkWZ-DtU0/edit
Please let me know what changes or clarity in wording you would like as I'm assuming
it needs some changes including from Richard.
Thanks,
Nick
reply other threads:[~2019-03-27 22:14 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=30e46a16-5801-e787-30e9-c7c68a0dab8b@gmail.com \
--to=xerofoify@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=rguenther@suse.de \
/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).