Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Dave Love <d.love@liverpool.ac.uk>
Cc: ding@gnus.org
Subject: Re: Emacsen supported
Date: Mon, 05 Jan 2009 21:48:47 +0100	[thread overview]
Message-ID: <87ljtpscls.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871vvhohuq.fsf@liv.ac.uk> (Dave Love's message of "Mon, 05 Jan 2009 16:09:01 +0000")

On Mon, Jan 05 2009, Dave Love wrote:

> 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

I though I already responded, but the message was still in my drafts
folder.  Sorry.

> whether it is still supposed to be supported to avoid me wasting
> time on Emacs 21 support,

Yes, it is supposed to be supported.  I don't test with Emacs 21 (nor
XEmacs) though.  The major reason not to drop support for Emacs 21 is
that we won't gain much because often the same code is necessary for
XEmacs 21.4 (and 21.5).

> like a different fix for this inconsistent `declare' if requiring cl
> isn't acceptable?

I've committed this:

;; Only necessary for `declare' when compiling Gnus with Emacs 21.
(eval-when-compile (require 'cl))

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2009-01-05 20:48 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     ` Emacsen supported (was: fix for time-date.el) Dave Love
2009-01-05 19:17       ` Emacsen supported Steinar Bang
2009-01-05 20:48       ` Reiner Steib [this message]
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=87ljtpscls.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=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).