From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: rfc2231 bug
Date: Tue, 18 Apr 2006 09:06:23 +0900 [thread overview]
Message-ID: <b4mk69nu4qo.fsf@jpl.org> (raw)
In-Reply-To: <b4mzmijvl3y.fsf@jpl.org>
>>>>> In <b4mzmijvl3y.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> The most recent changes in rfc2231-parse-string cause a bug.
I found there's one more bug in rfc2231.el, though it is
irrelevant to the recent changes because yesterday's version
doesn't solve it. The bug was reported by Reiner Steib and I
once fixed[1]. However, I might have enbugged after that.
[1]
http://news.gmane.org/group/gmane.emacs.gnus.general/thread=60638/force_load=t
I'll look into it (but I have no time nowadays, so I appreciate
someone debugging it).
next prev parent reply other threads:[~2006-04-18 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 23:27 Katsumi Yamaoka
2006-04-18 0:06 ` Katsumi Yamaoka [this message]
2006-04-18 8:00 ` Katsumi Yamaoka
2006-04-18 16:28 ` 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=b4mk69nu4qo.fsf@jpl.org \
--to=yamaoka@jpl.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).