From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Restore broken multipart headers (patch: 89-zsh5)
Date: 01 Jul 1999 12:02:35 -0400 [thread overview]
Message-ID: <2niu84pdd0.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m37lokbqer.fsf@vvv.vsu.ru>
>>>>> "VVV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VVV> "ZSH" == Shenghuo ZHU writes:
ZSH> If you get a multipart message but the MIME headers are removed
ZSH> by some agent, this patch enables pgnus display it as original
ZSH> one by pressing 'W M r' or clicking menu 'Article/MIME/Broken
ZSH> multipart'.
VVV> But there already exists something very similar:
VVV> gnus-summary-repair-multipart (`K m' in summary buffer).
I did not know that.
VVV> so imho only one of these functions should be left (i do not like that
VVV> gnus-summary-repair-multipart always tries to replace an article).
You are right. Please ignore the patch.
--
Shenghuo ZHU
prev parent reply other threads:[~1999-07-01 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 9:17 Shenghuo ZHU
1999-07-01 10:44 ` Vladimir Volovich
1999-07-01 16:02 ` Shenghuo ZHU [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=2niu84pdd0.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.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).