From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: multipart/related?
Date: 29 Nov 1998 16:08:00 +0100 [thread overview]
Message-ID: <m3lnkur0z3.fsf@sparky.gnus.org> (raw)
In-Reply-To: wmperry@aventail.com's message of "29 Nov 1998 00:14:04 -0500"
wmperry@aventail.com (William M. Perry) writes:
> Is there any way to signal gnus that a certain content-id has been
> 'consumed' and that it shouldn't display it?
The multipart/related RFC seems to say that a multipart/related-aware
reader should only display the "base" part, and that base part is
supposed to include all the other parts inside of it. So I've made
that change to 0.56.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-11-29 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-29 5:14 multipart/related? William M. Perry
1998-11-29 15:08 ` 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=m3lnkur0z3.fsf@sparky.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).