From: "Russ Cox" <rsc@mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] process migration
Date: Thu, 18 Sep 2003 09:25:15 -0400 [thread overview]
Message-ID: <f435bfea430a0402bf953a4b556a7565@plan9.bell-labs.com> (raw)
In-Reply-To: <181e352f.0309172305.5c4b343d@posting.google.com>
No, there is no process migration.
Russ
next prev parent reply other threads:[~2003-09-18 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 9:08 Kamal R. Prasad
2003-09-17 9:17 ` Fco.J.Ballesteros
2003-09-17 13:38 ` Ishwar Rattan
2003-09-18 8:58 ` Kamal R. Prasad
2003-09-18 13:25 ` Russ Cox [this message]
2003-09-18 13:38 ` ron minnich
2003-09-18 14:08 ` Charles Forsyth
2003-09-17 13:39 ` ron minnich
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=f435bfea430a0402bf953a4b556a7565@plan9.bell-labs.com \
--to=rsc@mit.edu \
--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).