From: Diego Novillo <dnovillo@google.com>
To: Philip Herron <redbrain@gcc.gnu.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Google Summer of Code 2011 Doc Camp 17 October - 21 October
Date: Tue, 12 Jul 2011 17:59:00 -0000 [thread overview]
Message-ID: <4E1C8477.2020902@google.com> (raw)
In-Reply-To: <CAEvRbeqKE-EwhdPEnPCDdp3iaD-r_2m-Yoo12s8zv+KP4CBPCw@mail.gmail.com>
On 11-07-12 12:52 , Philip Herron wrote:
> Would Gcc internals documentation count or is it more for a whole
> project documentation work? I probably missed the thing about this in
> London since i had to leave on the Sunday morning.
>
> I am kind of interested but i am unsure what kind of documentation
> would be appropriate i've spent the last few days working on some
> internals documentation on and off so its kind of fresh in my mind.
Any kind of documentation is fine. Internals, user documentation, etc.
Diego.
next prev parent reply other threads:[~2011-07-12 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEkQO63sEoCU1Q748B9MfiKbf_PEzjwoXs_zh-sAL826oK=fvg@mail.gmail.com>
2011-07-12 16:05 ` Fwd: " Diego Novillo
2011-07-12 17:11 ` Philip Herron
2011-07-12 17:59 ` Diego Novillo [this message]
2011-07-13 11:42 ` Philip Herron
2011-07-13 12:31 ` Diego Novillo
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=4E1C8477.2020902@google.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=redbrain@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).