From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: ERT tests on Emacs22
Date: Wed, 18 May 2011 15:46:17 -0500 [thread overview]
Message-ID: <87liy33ffq.fsf@lifelogs.com> (raw)
In-Reply-To: <m2pqnghvcv.fsf@ibookg4-c2.pc.gwdg.de>
On Wed, 18 May 2011 17:38:40 +0200 David Engster <deng@randomsample.de> wrote:
DE> Perfectly fine with me; I'll drop the registry tests for Emacs22
DE> then. BTW, XEmacs doesn't have the native serializer either; but as you
DE> said, no one's complained yet...
I'm OK with dropping the registry tests for both those platforms.
I'm sure XEmacs has a native hashtable serializer, though. EIEIO should
be patched to use it.
Ted
next prev parent reply other threads:[~2011-05-18 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2sjsedbvk.fsf@engster.org>
2011-05-18 14:52 ` Ted Zlatanov
2011-05-18 15:38 ` David Engster
2011-05-18 20:46 ` Ted Zlatanov [this message]
2011-05-19 6:51 ` David Engster
2011-05-19 10:11 ` Ted Zlatanov
2011-05-19 6:25 ` Gnus registry and Emacs <= 23.1 (was: ERT tests on Emacs22) Reiner Steib
2011-05-19 10:08 ` Gnus registry and Emacs <= 23.1 Ted Zlatanov
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=87liy33ffq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).