From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Josh Triplett <josh@kernel.org>
Subject: Sparse and the Google Summer of Code 2008
Date: Tue, 11 Mar 2008 20:38:35 +0300 [thread overview]
Message-ID: <f19298770803111038o3655a216vfe5a4b46876e7218@mail.gmail.com> (raw)
Hello.
Is sparse going to participate in this year's soc?
I e-mailed Josh a day or two ago, but got no answer,
and the org application deadline is May 12, 12:00 PDT.
I know, last year was not all that successful, but maybe
there will be more applications this year. I've got some
ideas about abstract interpretation for one. I can't promise
that I'll choose sparse, there should be lots of interesting
projects this year, but there are other people as well.
next reply other threads:[~2008-03-11 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 17:38 Alexey Zaytsev [this message]
2008-03-11 18:20 ` Sparse and the Google Summer of Code 2008 Josh Triplett
2008-03-11 19:08 ` James Westby
2008-03-11 22:10 ` Christopher Li
2008-03-12 1:41 ` Derek M Jones
2008-03-12 2:20 ` Alexey Zaytsev
2008-03-12 4:28 ` Josh Triplett
2008-03-12 15:19 ` Neil Booth
2008-03-12 20:01 ` Josh Triplett
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=f19298770803111038o3655a216vfe5a4b46876e7218@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.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).