From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme 3-1
Date: Tue, 18 Feb 2003 07:19:47 -0500 [thread overview]
Message-ID: <b6c7d17a90344fae8b80db57fbc0deac@plan9.bell-labs.com> (raw)
In-Reply-To: <bb33387ba10c28c1509365297565d34f@vitanuova.com>
> what currently depends on the fan-out behaviour of plumbing?
> (mail/fs, i guess, when messages are deleted, but that's very slow,
> and works without plumbing anyway).
faces and Mail depend on both getting announcements
about new messages from upas/fs via the plumber to
work correctly.
next prev parent reply other threads:[~2003-02-18 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 12:12 rog
2003-02-18 12:19 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 1:12 okamoto
2003-02-18 19:41 rog
2003-02-18 13:21 rog
2003-02-18 13:38 ` Russ Cox
2003-02-18 17:04 ` rob pike, esq.
2003-02-18 8:05 peter a. cejchan
2003-02-18 1:48 rob pike, esq.
2003-02-18 12:19 ` paurea
2003-02-18 14:10 ` Sam
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=b6c7d17a90344fae8b80db57fbc0deac@plan9.bell-labs.com \
--to=rsc@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).