From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Running Version 2 along with Version 3
Date: Mon, 29 Jan 2001 14:35:24 -0500 [thread overview]
Message-ID: <20010129193553.C6DE3199DD@mail.cse.psu.edu> (raw)
It's hard, yes, but we have an elegant solution involving
compiling code on the fly in the trap handler.
-rob
next reply other threads:[~2001-01-29 19:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 19:35 rob pike [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 15:07 rob pike
2001-01-30 21:41 geoff
2001-01-30 19:24 forsyth
2001-01-30 14:30 rob pike
2001-01-30 14:59 ` Mike Acar
2001-01-30 18:23 ` Boyd Roberts
2001-01-30 18:42 ` Mike Acar
2001-01-30 18:43 ` Christian Smith
2001-01-31 10:20 ` Bobby Dimmette
2001-01-30 10:51 forsyth
2001-01-30 14:23 ` Mike Acar
2000-06-20 14:51 presotto
2001-01-29 18:30 ` splite
2001-01-29 18:52 ` Mike Acar
2001-01-29 19:29 ` Boyd Roberts
2000-06-20 13:58 Bill Gunshannon
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=20010129193553.C6DE3199DD@mail.cse.psu.edu \
--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).