From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: CRLF canonicalization only done for text/plain
Date: Sat, 03 Sep 2005 13:04:13 +0200 [thread overview]
Message-ID: <v9irxiv2du.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <iluu0h3oq6h.fsf@latte.josefsson.org>
On Fri, Sep 02 2005, Simon Josefsson wrote:
> Hrvoje Niksic <hniksic@xemacs.org> writes:
>
>> Hopefully the above should be enough to convince you that Gnus does
>> not currently do the right thing. Fortunately the change is simple
>> enough, implemented by applying the patch below. Please let me know
>> if you agree with this change.
>
> You convinced me, so I applied your patch. RFC 2045 section 6.5 and
> 6.7 (4) also appear to discuss this. Thanks for the detailed
> investigation.
Shouldn't this go to the v5-10 branch too?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-09-03 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 23:35 Hrvoje Niksic
2005-09-02 7:59 ` Simon Josefsson
2005-09-03 11:04 ` Reiner Steib [this message]
2005-09-03 11:21 ` Simon Josefsson
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=v9irxiv2du.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).