From: Dave Love <d.love@liverpool.ac.uk>
To: ding@gnus.org
Subject: Emacsen supported (was: fix for time-date.el)
Date: Mon, 05 Jan 2009 16:09:01 +0000 [thread overview]
Message-ID: <871vvhohuq.fsf@liv.ac.uk> (raw)
In-Reply-To: <878wpyn10c.fsf@liv.ac.uk>
I wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> Did you test with Emacs 21?
>
> Yes. I thought it was supposed still to be supported -- that's what the
> gnus-coding Info file says.
Could someone tell me whether it is still supposed to be supported to
avoid me wasting time on Emacs 21 support, like a different fix for this
inconsistent `declare' if requiring cl isn't acceptable?
next prev parent reply other threads:[~2009-01-05 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87abam99gx.fsf@liv.ac.uk>
2008-12-23 16:41 ` fix for time-date.el Reiner Steib
2008-12-29 21:07 ` Dave Love
2009-01-05 16:09 ` Dave Love [this message]
2009-01-05 19:17 ` Emacsen supported Steinar Bang
2009-01-05 20:48 ` Reiner Steib
2009-01-05 23:27 ` Dave Love
2009-01-05 20:41 ` fix for time-date.el Reiner Steib
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=871vvhohuq.fsf@liv.ac.uk \
--to=d.love@liverpool.ac.uk \
--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).