From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Tue, 21 May 2013 23:01:54 +0200 [thread overview]
Message-ID: <87ppwkavy5.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <b4mli79ury3.fsf@jpl.org>
Hi Katsumi.
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> ?\« is ok for XEmacs 21.4 if it loads the Mule-UCS package that
> provides the utf-8 coding system.
But wouldn't just "171" work as well? Then we don't have to worry about
Mule-UCS etc.
I am probably putting my ignorance on display here... :-)
> BTW, isn't it possible for Gnus to drop the XEmacs 21.4 support?
I don't know - I was just checking to see if I could make the buildbot
go green. It feels like a waste to have a buildbot if red builds are
ignored for longer periods of time.
I guess XEmacs 21.5 won't be released this decade either... O:-)
Best regards,
Adam
--
"Hur långt man än har kommit Adam Sjøgren
är det alltid längre kvar" asjo@koldfront.dk
next prev parent reply other threads:[~2013-05-21 21:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 19:23 Adam Sjøgren
2013-05-19 21:45 ` Mike Kupfer
2013-05-19 21:58 ` Adam Sjøgren
2013-05-19 22:13 ` Adam Sjøgren
2013-05-19 23:30 ` Adam Sjøgren
2013-05-20 7:39 ` David Engster
2013-05-20 16:01 ` Adam Sjøgren
2013-05-20 16:36 ` Adam Sjøgren
2013-05-20 23:55 ` Katsumi Yamaoka
2013-05-21 21:01 ` Adam Sjøgren [this message]
2013-05-21 23:39 ` Katsumi Yamaoka
2013-05-22 2:58 ` Mike Kupfer
2013-05-22 5:45 ` Katsumi Yamaoka
2013-05-28 0:22 ` Mike Kupfer
2013-05-31 12:07 ` Mats Lidell
2013-05-22 20:18 ` Adam Sjøgren
2013-05-22 20:28 ` Adam Sjøgren
2013-05-22 20:36 ` David Engster
2013-05-28 0:43 ` Mike Kupfer
2013-06-01 22:04 ` XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el) Mike Kupfer
2013-06-02 8:59 ` David Engster
2013-06-02 16:22 ` Mike Kupfer
2013-06-06 14:46 ` Ted Zlatanov
2013-06-06 16:06 ` Mike Kupfer
2013-05-22 3:02 ` XEmacs builds failing - gnus-spec.el Mike Kupfer
2013-05-22 20:25 ` David Engster
2013-05-28 0:25 ` Mike Kupfer
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=87ppwkavy5.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).