From: Dave Love <d.love@dl.ac.uk>
Subject: Re: rfc2047 patch broke Gnus on XEmacsc
Date: 04 May 2003 12:20:11 +0100 [thread overview]
Message-ID: <rzqn0i33qms.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <87u1ccnyi6.fsf@orebokech.com>
Romain FRANCOISE <romain@orebokech.com> writes:
> I'm wondering if Dave's changes really apply as "bugfixes only",
It's clearly a bug to send badly-encoded messages. MTAs even bounce
them, which is why I went to the trouble to fix it. I'm also trying
to get it into a better state for inclusion in Emacs, allow using the
components separately, and merge changes which are in the Emacs
sources. The mess around Gnus 5.9 shouldn't be repeated.
next prev parent reply other threads:[~2003-05-04 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 8:57 Andreas Jaeger
2003-05-03 9:57 ` Romain FRANCOISE
2003-05-03 12:44 ` Raymond Scholz
2003-05-04 11:20 ` Dave Love [this message]
2003-05-03 13:40 ` Simon Josefsson
2003-05-03 15:00 ` Vasily Korytov
2003-05-04 11:22 ` Dave Love
[not found] ` <rzqsmrv3r11.fsf@albion.dl.ac.uk>
2003-05-04 12:26 ` Andreas Jaeger
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=rzqn0i33qms.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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).