Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: miles@gnu.org, "Katsumi Yamaoka" <yamaoka@jpl.org>, ding@gnus.org
Subject: Re: CVS update of gnus/lisp (7 files)
Date: 13 Dec 2004 13:39:16 -0500	[thread overview]
Message-ID: <4nr7lu82ln.fsf@lifelogs.com> (raw)
In-Reply-To: <fc339e4a041207172716df605b@mail.gmail.com> (Miles Bader's message of "Wed, 8 Dec 2004 10:27:01 +0900")

On Wed, 8 Dec 2004, snogglethorpe@gmail.com wrote:

>> The recent changes in gnus-registry.el[1], gnus-util.el[2],
>> message.el[3] and pop3.el[4] are unwanted for the Gnus trunk
>> because:
> 
> 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.

I think supporting Emacs 20 is, realistically speaking, not desirable
because of the many useful functions in Emacs 21 (like puthash) we'd
have to emulate.  Yes, it can be done in every source file, but why
not just have a gnus-c20.el or something like that to provide the
compatibility layer to Emacs 20?  Moreover, is there a sizeable Emacs
20 user base we want to support rather than force into upgrading?

I don't know the answers to the last question :)  It seems to me from
discussions here and on emacs-devel, however, that the answer is "no."

Ted



  parent reply	other threads:[~2004-12-13 18:39 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 ` Katsumi Yamaoka
2004-12-08  1:27   ` Miles Bader
2004-12-08  3:01     ` Katsumi Yamaoka
2004-12-13 18:39     ` Ted Zlatanov [this message]
2004-12-13 23:49       ` Supported (X)Emacs version (was: CVS update of gnus/lisp (7 files)) 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=4nr7lu82ln.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=miles@gnu.org \
    --cc=yamaoka@jpl.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).