Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Supported (X)Emacs version (was: CVS update of gnus/lisp (7 files))
Date: Tue, 14 Dec 2004 00:49:58 +0100	[thread overview]
Message-ID: <v9acshhi6x.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nr7lu82ln.fsf@lifelogs.com>

On Mon, Dec 13 2004, Ted Zlatanov wrote:

> On Wed, 8 Dec 2004, snogglethorpe@gmail.com wrote:
[...]
>> Is there a policy that the Gnus trunk doesn't support old versions
>> of Emacs?
>
> I think the general policy is to code for the latest official Emacs.
> Backwards compatibility is nice but not imperative.  This is just my
> understanding, though.

The official policy is written in (info "(gnus)Emacsen"):

,----[ (info "(gnus)Emacsen") ]
| Gnus should work on:
| 
|    * Emacs 21.1 and up.
| 
|    * XEmacs 21.4 and up.
| 
|    This Gnus version will absolutely not work on any Emacsen older than
| that.  Not reliably, at least.  Older versions of Gnus may work on older
| Emacs versions.
`----

For the Gnus 5.10 series (and thus the v5-10 branch) it's Emacs 20.7
and XEmacs 21.1.  When starting No Gnus, everyone on this list agreed
that we should drop support for Emacs 20 and XEmacs 21.1 because
supporting those outdated versions makes the code less readable and
harder to maintain (IIRC).

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




      reply	other threads:[~2004-12-13 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CbpKS-0001C7-00@quimby.gnus.org>
2004-12-08  1:17 ` CVS update of gnus/lisp (7 files) Katsumi Yamaoka
2004-12-08  1:27   ` Miles Bader
2004-12-08  3:01     ` Katsumi Yamaoka
2004-12-13 18:39     ` Ted Zlatanov
2004-12-13 23:49       ` Reiner Steib [this message]

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=v9acshhi6x.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).