From: jim <jim.whitson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>,
Russ Cox <russcox@gmail.com>
Subject: Re: [9fans] Acme mailreader
Date: Wed, 15 Dec 2004 18:49:03 +0000 [thread overview]
Message-ID: <FD92FD5B-4EC9-11D9-901F-00112430C042@gmail.com> (raw)
In-Reply-To: <ee9e417a04121510337da43952@mail.gmail.com>
On 15 Dec 2004, at 18:33, Russ Cox wrote:
>> Ah I see. So, this magic 9p socket(s) lets acme talk to upas/fs in
>> order to get the (nicely decoded) emails? Very good. So, upas/fs
>
> actually acme talks to Mail which talks to upas/fs, but yeah.
>> maintains some kind of internal representation of the /mnt/fs/mbox?
>
> this.
>
>
Cool. It's much clearer now. There seems to be a very complete
porting guide in cmd/upas/README, so my life is much easier
now :-).
Cheers,
jim
next prev parent reply other threads:[~2004-12-15 18:49 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 15:34 jim
2004-12-15 15:40 ` gdiaz
2004-12-15 15:47 ` jim
2004-12-15 15:50 ` Joseph Stewart
2004-12-15 15:57 ` jim
2004-12-15 16:10 ` Russ Cox
2004-12-15 15:58 ` Charles Forsyth
2004-12-15 16:04 ` jim
2004-12-15 16:24 ` C H Forsyth
2004-12-15 16:31 ` jim
2004-12-15 17:07 ` Russ Cox
2004-12-15 17:30 ` jim
2004-12-15 18:33 ` Russ Cox
2004-12-15 18:49 ` jim [this message]
2004-12-15 18:36 ` Axel Belinfante
2004-12-15 18:47 ` jim
2004-12-15 18:51 ` rog
2004-12-15 18:48 ` Skip Tavakkolian
2004-12-15 16:05 ` rog
2004-12-15 16:07 ` rog
2004-12-15 16:09 ` jim
2004-12-16 0:24 ` geoff
2004-12-16 4:12 ` Ronald G. Minnich
2004-12-16 4:51 ` geoff
2004-12-16 9:25 ` jim
2004-12-16 5:13 ` Skip Tavakkolian
2004-12-16 5:17 ` geoff
2004-12-16 5:20 ` boyd, rounin
2004-12-16 5:34 ` boyd, rounin
2004-12-16 5:29 ` Skip Tavakkolian
2004-12-16 15:54 ` Ronald G. Minnich
2004-12-16 17:52 ` Skip Tavakkolian
2004-12-16 18:13 ` Dave Eckhardt
2004-12-16 5:23 ` Andy Newman
2004-12-16 15:52 ` Ronald G. Minnich
2004-12-16 8:17 ` Martin C.Atkins
2004-12-16 9:35 ` jim
2004-12-16 15:19 ` rog
2004-12-16 15:26 ` jim
2004-12-16 9:30 ` jim
2004-12-16 15:08 ` David Leimbach
2004-12-16 23:22 ` geoff
2004-12-16 23:25 ` boyd, rounin
2004-12-16 23:38 ` Ronald G. Minnich
2004-12-17 1:31 ` Skip Tavakkolian
2004-12-17 15:50 ` Ronald G. Minnich
2004-12-17 4:55 ` [9fans] Acme mailreader - now: User mode filesystems in linux Martin C.Atkins
2004-12-17 9:54 ` Martin C.Atkins
2004-12-17 10:22 ` geoff
2004-12-17 10:45 ` Martin C.Atkins
2004-12-17 11:42 ` Andy Newman
2004-12-17 15:57 ` Ronald G. Minnich
2004-12-17 12:30 ` Latchesar Ionkov
2004-12-17 15:55 ` Ronald G. Minnich
2004-12-17 13:41 ` Derek Fawcus
2004-12-17 14:42 ` Karl Magdsick
2004-12-17 14:56 ` Russ Cox
2004-12-18 0:13 ` Tim Newsham
2004-12-18 0:13 ` boyd, rounin
2004-12-18 3:49 ` Ronald G. Minnich
2004-12-23 16:04 ` boyd, rounin
2004-12-17 15:44 ` Ronald G. Minnich
2004-12-18 12:35 ` Martin C.Atkins
2004-12-17 18:52 ` [9fans] Acme mailreader David Leimbach
2004-12-17 23:20 ` Jack Johnson
2004-12-18 1:00 ` David Leimbach
2004-12-15 16:09 ` Russ Cox
2004-12-15 16:16 ` jim
2004-12-15 16:22 ` boyd, rounin
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=FD92FD5B-4EC9-11D9-901F-00112430C042@gmail.com \
--to=jim.whitson@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).