From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Permissions, again
Date: Wed, 15 May 2002 14:25:15 -0400 [thread overview]
Message-ID: <9c80852c69419df6be753b662554f2a4@plan9.bell-labs.com> (raw)
> Nothing's really impossible,
It is impossible to eat the sun. (It may be possible to eat a SUN workstation,
but that's not what I mean.)
-rob
next reply other threads:[~2002-05-15 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 18:25 rob pike, esq. [this message]
2002-05-15 18:31 ` Sam
2002-05-16 9:06 ` Don
2002-05-15 20:50 ` Dan Cross
2002-05-15 21:01 ` Chris Hollis-Locke
2002-05-15 21:20 ` Dan Cross
2002-05-16 19:00 ` Matt H
[not found] <20020516192637.3C3F33408A@bolivar.ugcs.caltech.edu>
2002-05-16 21:49 ` matt
2002-05-17 9:10 ` Don
-- strict thread matches above, loose matches on Subject: below --
2002-05-15 20:56 rob pike, esq.
2002-05-15 18:20 rsc
2002-05-15 18:23 ` Scott Schwartz
2002-05-15 15:22 Lucio De Re
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=9c80852c69419df6be753b662554f2a4@plan9.bell-labs.com \
--to=rob@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).