From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] from slashdot
Date: Thu, 18 Aug 2005 10:08:57 -0400 [thread overview]
Message-ID: <548024f26742f4d23d70e43369729201@plan9.bell-labs.com> (raw)
In-Reply-To: <3d994e7e2c26be3e7dd3a7e4163c7c28@vitanuova.com>
>>>I don't anticipate any change to the sources and web infrastructure.
>
> i thought the more important thing would be
> what might happen to the espresso machine.
Don't worry about that. We will hang on to that if it's the last thing we do.
Sape
next prev parent reply other threads:[~2005-08-18 14:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 19:28 Trickey, Howard W (Howard)
2005-08-18 11:20 ` C H Forsyth
2005-08-18 11:30 ` Nigel Roles
2005-08-18 13:12 ` Joel Salomon
2005-08-18 13:46 ` Eric Van Hensbergen
2005-08-18 14:08 ` Sape Mullender [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-17 4:22 andrey mirtchovski
2005-08-17 5:04 ` Tim Newsham
2005-08-17 13:39 ` Sape Mullender
2005-08-17 13:26 ` Sape Mullender
2005-08-17 13:38 ` Vester Thacker
2005-08-17 13:40 ` Charles Forsyth
2005-08-17 16:26 ` Skip Tavakkolian
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=548024f26742f4d23d70e43369729201@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).