Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: [Richard Stallman <rms@gnu.org>] rfc2047.el
Date: Sun, 27 Oct 2002 09:43:59 -0500	[thread overview]
Message-ID: <2n3cqsndqo.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <848z0k2exs.fsf@crybaby.uni-duisburg.de> (kai.grossjohann@uni-duisburg.de's message of "Sun, 27 Oct 2002 14:23:43 +0100")

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Does the patch apply to Oort?  I think the patch was made for Emacs
>> 21.3, and a thread in gnus.gnus-bug said this was already fixed in
>> Oort but differently, but I may be mistaken.  (None of the solutions
>> does the right thing; implement a RFC 2822 parser to tokenize and then
>> QP only the correct tokens....)
>
> Hm.  I don't know all this stuff.  If anyone knows, please holler.

I checked Dave's previous patch in Sep 13. Because some problems had
been fixed before, I only merged some changes of Dave's previous patch
into Oort Gnus.  The message id of the previous patch is
<rzqn0qxc2yb.fsf@albion.dl.ac.uk> .  I didn't check the new one.

I agree with Simon.  But I don't have much time to fix bugs in the
next three or four months.  Anyone volunteers to fix the bug?  I think
we need a bunch of test cases to make sure that a new fixing doesn't
bring new bugs.

ShengHuo



  reply	other threads:[~2002-10-27 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27  8:56 Kai Großjohann
2002-10-27 12:16 ` Simon Josefsson
2002-10-27 13:23   ` Kai Großjohann
2002-10-27 14:43     ` ShengHuo ZHU [this message]
2002-12-28 22:06   ` Lars Magne Ingebrigtsen

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=2n3cqsndqo.fsf@zsh.cs.rochester.edu \
    --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).