From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lucio- now: student projects
Date: Tue, 12 Mar 2002 12:28:06 +0000 [thread overview]
Message-ID: <20020312123158.1C2E619988@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 23 bytes --]
excessive optimism?
[-- Attachment #2: Type: message/rfc822, Size: 1884 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lucio- now: student projects
Date: Tue, 12 Mar 2002 12:04:29 0000
Message-ID: <20020312120527.9B66919A0D@mail.cse.psu.edu>
> (i'm not using the Unicode 1/2 because of some stupid mail gateways)
I wonder why upas/marshal uses Content-Transfer-Encoding: 8bit rather than
quoted-printable for non-ascii message bodies? What is the relative
likelihood of mail gateways not handling the former vs mail readers not
handling the latter?
-- Richard
next reply other threads:[~2002-03-12 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 12:28 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 14:59 andrey mirtchovski
2002-03-12 12:04 Richard Miller
2002-03-12 10:13 forsyth
2002-03-12 13:08 ` Martin C.Atkins
2002-03-05 0:10 [9fans] lucio- geoff
2002-03-11 10:05 ` Luis Fernandes
2002-03-12 7:17 ` [9fans] lucio- now: student projects Martin C.Atkins
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=20020312123158.1C2E619988@mail.cse.psu.edu \
--to=forsyth@caldo.demon.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).