From: Jacob Todd <jaketodd422@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Google code-in?
Date: Fri, 5 Nov 2010 15:23:13 -0400 [thread overview]
Message-ID: <AANLkTik5c3jqTxvVQqN9NhnJoG2mmnTOLCrYJggk822H@mail.gmail.com> (raw)
In-Reply-To: <87b9b103c90c4b98f0a3cc8e36f69fef@swcp.com>
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
Code-in? Could you elaborate?
On Nov 5, 2010 1:22 PM, "EBo" <ebo@sandien.com> wrote:
> Google just announced a code-in. Is Plan9 participating?
>
> EBo --
>
>
[-- Attachment #2: Type: text/html, Size: 316 bytes --]
next prev parent reply other threads:[~2010-11-05 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 17:21 EBo
2010-11-05 19:23 ` Jacob Todd [this message]
2010-11-05 20:00 ` Nick LaForge
2010-11-05 20:43 ` erik quanstrom
2010-11-05 21:27 ` Nick LaForge
2010-11-05 22:51 ` EBo
2010-11-05 22:47 ` EBo
2010-11-12 11:14 ` Eris Discordia
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=AANLkTik5c3jqTxvVQqN9NhnJoG2mmnTOLCrYJggk822H@mail.gmail.com \
--to=jaketodd422@gmail.com \
--cc=9fans@9fans.net \
/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).