From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: XEmacs, Gnus and mm-coding-system priorities.
Date: Sat, 18 Dec 2004 01:09:22 +0900 [thread overview]
Message-ID: <yotlwtvgc3f1.fsf@jpl.org> (raw)
In-Reply-To: <b9yoegtnlck.fsf@jpl.org>
>>>>>> In <16834.53068.586526.338568.dm0@vm.parhasard.net> Aidan Kehoe wrote:
>> That’s done. It may take a few days more than normal to get to
>> Massachusetts, though, because our postal service isn’t up to much.
>>>>> In <b9yoegtnlck.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> Thanks. I'll do it ASAP (tomorrow in Japan, maybe).
This is tomorrow of the day. :)
I've installed Aidan Kehoe's change in both the trunk and
the v5-10 branch.
next prev parent reply other threads:[~2004-12-17 16:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 16:55 Aidan Kehoe
2004-12-06 2:30 ` Katsumi Yamaoka
2004-12-06 13:35 ` Aidan Kehoe
2004-12-06 15:19 ` Katsumi Yamaoka
2004-12-06 22:30 ` Katsumi Yamaoka
2004-12-07 1:03 ` Katsumi Yamaoka
2004-12-07 0:10 ` Aidan Kehoe
2004-12-07 1:04 ` Katsumi Yamaoka
2004-12-07 12:32 ` Katsumi Yamaoka
2004-12-17 12:21 ` Aidan Kehoe
2004-12-17 12:46 ` Katsumi Yamaoka
2004-12-17 16:09 ` Katsumi Yamaoka [this message]
2004-12-31 9:01 ` XEmacs hangs in rfc2047-encode-string (Was: XEmacs, Gnus and mm-coding-system priorities.) Steinar Bang
2004-12-31 11:47 ` XEmacs hangs in rfc2047-encode-string Reiner Steib
2004-12-31 14:41 ` Steinar Bang
2004-12-31 19:10 ` Andrey Slusar
2005-01-01 9:04 ` Steinar Bang
2005-01-01 18:03 ` Andrey Slusar
2005-01-01 19:25 ` Steinar Bang
2005-01-01 22:05 ` Andrey Slusar
2005-01-02 7:49 ` Steinar Bang
2004-12-31 12:53 ` Steinar Bang
2004-12-31 13:42 ` Arnaud Giersch
2004-12-31 14:45 ` Steinar Bang
2004-12-07 1:03 ` XEmacs, Gnus and mm-coding-system priorities Katsumi Yamaoka
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=yotlwtvgc3f1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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).