From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: p0.88 misparses 2nd-level message forwarding
Date: 28 Jun 1999 19:32:08 +0200 [thread overview]
Message-ID: <m39094w7s7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Karl Kleinpaste's message of "22 Jun 1999 21:28:47 -0400"
Karl Kleinpaste <karl@justresearch.com> writes:
> Interesting point. So the conclusion is simply to number them
> sequentially?
That's what seems to make the most sense in an Emacs context.
> That works fine for me, but I thought we were up against some sort
> of MIME RFC requirement to force a hierarchical view somehow.
I don't think the RFCs say anything about that...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-06-28 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 21:14 Karl Kleinpaste
1999-06-23 1:10 ` Shenghuo ZHU
1999-06-23 1:28 ` Karl Kleinpaste
1999-06-28 17:32 ` Lars Magne Ingebrigtsen [this message]
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=m39094w7s7.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).