From: Steinar Bang <sb@metis.no>
Subject: Re: RFC 2646
Date: 11 Oct 1999 10:06:12 +0200 [thread overview]
Message-ID: <wh7lku5nkb.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Per Abrahamsen's message of "09 Oct 1999 23:19:12 +0200"
>>>>> Per Abrahamsen <abraham@dina.kvl.dk>:
> After pGnus is released, I think RFC 2646 support would be a good
> thing to work on. It solves some of the worst shortcommings of
> text/plain in a backward compatible way.
http://www.ietf.org/rfc/rfc2646.txt
Title: The Text/Plain Format Parameter
next prev parent reply other threads:[~1999-10-11 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-09 21:19 Per Abrahamsen
1999-10-11 8:06 ` Steinar Bang [this message]
1999-10-11 8:11 ` Steinar Bang
1999-10-11 13:06 ` Per Abrahamsen
1999-10-12 8:19 ` Steinar Bang
1999-10-11 12:08 ` Toby Speight
1999-10-11 13:11 ` Per Abrahamsen
1999-11-06 20:54 ` Lars Magne Ingebrigtsen
1999-11-06 21:23 ` Per Abrahamsen
1999-11-07 3:22 ` Lars Magne Ingebrigtsen
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=wh7lku5nkb.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).