9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, uriel@cat-v.org, russ cox <rsc@swtch.com>
Subject: Re: [9fans] acme mail on unix
Date: Fri, 20 Jan 2006 14:59:43 -0600	[thread overview]
Message-ID: <20060120205943.1D5BD1535C@dexter-peak.quanstro.net> (raw)
In-Reply-To: <eeda0c9a9ae7c0f9973850713433cccb@cat-v.org>

uriel,

my limited time is starting to cause major headaches.
i've been working with john cummings on getting upas
ready-for-primetime within plan9port. upas/fs has been
stable for a long time, but not integrated.

perhaps this is silly to worry about, but i'd rather not
have a version in contrib if it's not necessiary.

russ, would you be willing to integrate the recient p9p 
upas/fs changes ahead of the rest of upas? i believe that
it's ready.

these changes will probablly work with plan9 proper.
this isn't something i can test right now.

- erik

uriel@cat-v.org writes

| 
| > uriel@cat-v.org writes
| > | > i added mdir support to upas/fs for p9p. it should work
| > | > on mh directories, too.
| > | Do you think it might make it easier to change upas/fs to
| > | not keep the whole mailbox in memory?
| > 
| > yes, i do. but i didn't go that far.
| Ah, that is great news! That limitation is one of my main problems with upas/fs.
| 
| > | > this isn't integrated yet, but has worked pretty well for me.
| > | What is missing for it to be integrated into the distribution?
| > | 
| > | > set me a note if you'd like me to forward the code.
| > | Could you put it in sources/contrib?
| > 
| > i would, but i don't have a directory.
| Get one then ;) 
| 
| See:
| http://plan9.bell-labs.com/wiki/plan9/How_to_contribute/#SOURCES/CONTRIB
| 
| uriel


  reply	other threads:[~2006-01-20 20:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 16:46 Russ Cox
2006-01-18 17:56 ` Tim Wiess
2006-01-18 18:08   ` Tim Wiess
2006-01-18 19:10   ` Russ Cox
2006-01-19 16:17     ` Aaron Griffin
2006-01-19 16:24       ` Russ Cox
2006-01-19 21:28         ` Dan Cross
2006-01-19 21:58           ` Russ Cox
2006-01-20  2:38             ` geoff
2006-01-20  5:31               ` Scott Schwartz
2006-01-20  6:04                 ` John Barham
2006-01-20 13:50                   ` erik quanstrom
2006-01-20 23:01                     ` Dave Eckhardt
2006-01-21  0:06                       ` erik quanstrom
2006-01-20 13:58           ` erik quanstrom
2006-01-20 20:02             ` erik quanstrom
2006-01-20 20:12               ` uriel
2006-01-20 20:18                 ` erik quanstrom
2006-01-20 20:41                   ` uriel
2006-01-20 20:59                     ` erik quanstrom [this message]
2006-01-20 22:58 Russ Cox

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=20060120205943.1D5BD1535C@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=rsc@swtch.com \
    --cc=uriel@cat-v.org \
    /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).