From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: uriel@berlinblue.org
Subject: Re: [9fans] A new kind of Plan 9 FAQ
Date: Mon, 31 May 2010 19:17:19 -0700 [thread overview]
Message-ID: <AANLkTimtUGDHi1looqaSAPoQXsK1wNfNVt3PtJlm_1_r@mail.gmail.com> (raw)
In-Reply-To: <4C0467A2.8090508@Princeton.EDU>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
On Mon, May 31, 2010 at 6:51 PM, Martin Harriss <martin@princeton.edu>wrote:
> Uriel wrote:
>
>> I recently made a fascinating archeological discovery:
>>
>> http://doc.cat-v.org/plan_9/humour/shaneys-plan9-faq
>>
>> Enjoy!
>>
>> uriel
>>
>>
> Well that certainly clears it up for me.
>
> Markov Chains for the win.
[-- Attachment #2: Type: text/html, Size: 824 bytes --]
next prev parent reply other threads:[~2010-06-01 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 1:32 Uriel
2010-06-01 1:42 ` Jorden M
2010-06-01 1:51 ` Martin Harriss
2010-06-01 2:17 ` David Leimbach [this message]
2010-06-01 2:39 ` Justin Jackson
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=AANLkTimtUGDHi1looqaSAPoQXsK1wNfNVt3PtJlm_1_r@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
--cc=uriel@berlinblue.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).