From: Sverre Rabbelier <srabbelier@gmail.com>
To: P Baker <me@retrodict.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
Andreas Ericsson <ae@op5.se>
Subject: Re: [RFC] GSoC Proposal v2:
Date: Fri, 3 Apr 2009 06:22:29 +0200 [thread overview]
Message-ID: <fabb9a1e0904022122w4b11dbccr69a48f08c6f345a4@mail.gmail.com> (raw)
In-Reply-To: <526944450904022015n67be674dwfab5d3dc597c806b@mail.gmail.com>
Heya,
On Fri, Apr 3, 2009 at 05:15, P Baker <me@retrodict.com> wrote:
> See below for a revised project application. More comments would be
> appreciated. Thanks to Shawn, Dscho and Andreas for already offering
> some help!
In case you haven't noticed the announcement, please submit your
proposal for GSoC to http://socghop.appspot.com as soon as possible!
Thanks :).
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-04-03 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 3:15 [RFC] GSoC Proposal v2: P Baker
2009-04-03 4:22 ` Sverre Rabbelier [this message]
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=fabb9a1e0904022122w4b11dbccr69a48f08c6f345a4@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=me@retrodict.com \
--cc=spearce@spearce.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 NNTP newsgroup(s).