From: Anthony Sorace <a@9srv.net>
To: ebo@sandien.com, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC application template/examples
Date: Thu, 4 Mar 2010 17:53:10 -0500 [thread overview]
Message-ID: <E5D829C2-BFAC-466D-B401-59CC787CA6E6@9srv.net> (raw)
In-Reply-To: <twig.1267710809.512@swcp.com>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
> I should rephrase that -- are there any changes that should be made
> to the
> 2008 application template for current applications?
Yes. Overall, I think our template worked well, but it wasn't perfect.
In particular, I think we want to be a bit clearer about expectations
going in, and I think we want to make slightly higher demands of
applicants. I'll be posting a revision for discussion shortly.
Anthony Sorace
Strand 1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2010-03-04 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 13:53 EBo
2010-03-04 22:53 ` Anthony Sorace [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-04 13:48 EBo
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=E5D829C2-BFAC-466D-B401-59CC787CA6E6@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
--cc=ebo@sandien.com \
/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).