From: Matt H <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] upas/fs -f/imap faltering start
Date: Wed, 30 Jan 2002 00:32:27 +0000 [thread overview]
Message-ID: <20020130003227.2641ed50.matt@proweb.co.uk> (raw)
In-Reply-To: <20020130002340.DEAAE19A02@mail.cse.psu.edu>
On Tue, 29 Jan 2002 19:23:39 -0500
"Russ Cox" <rsc@plan9.bell-labs.com> wrote:
> it sounds like /sys/src/cmd/upas/fs/imap4.c:/^imap4resp
> should be ignoring lines that begin with INFO;
> i'd check the imap rfc 2060 to be sure.
> not a hard fix if so.
ta, saves me endlessly fiddling again!
well, until i find something new to fiddle with
M
next prev parent reply other threads:[~2002-01-30 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 0:23 Russ Cox
2002-01-30 0:32 ` Matt H [this message]
2002-02-06 0:42 ` Matt H
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 9:31 [9fans] Getting started in Plan9 - help Douglas A. Gwyn
2002-01-29 10:44 ` [OT] " paurea
2002-01-29 17:20 ` Thomas Bushnell, BSG
2002-01-30 0:20 ` [9fans] upas/fs -f/imap faltering start Matt H
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=20020130003227.2641ed50.matt@proweb.co.uk \
--to=matt@proweb.co.uk \
--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).