unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: dropping support for old Emacsen
Date: Sun, 08 Nov 2015 15:33:42 +0000	[thread overview]
Message-ID: <87h9kwqze1.fsf@mat.ucm.es> (raw)
In-Reply-To: 87h9kz17hb.fsf_-_@lifelogs.com

>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:

   > On Fri, 06 Nov 2015 11:22:22 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote: 
   KY> On Thu, 05 Nov 2015 15:03:59 -0500, Ted Zlatanov wrote:
   >>> Maybe drop Gnus support for Emacs 23.x and old XEmacs too?
   >>> I think we've had too many of these annoyances over the years.

   KY> making Gnus drop old Emacsen is a good idea. Probably dropping Emacs
   KY> 23 won't trouble many users. But what is old XEmacs to be? In some
   KY> sense, all XEmacsen is old. ;-)

I think 21.5.34 should be at least considered not dead...

   > I should note I've brought this up before. Crossposting to the Gnus
   > mailing list as well. Concretely, the proposal is to support only Emacs
   > 24.x in Gnus. If XEmacs or Emacs 23 support breaks, then users can
   > submit patches but it won't be a primary focus for the developers.

   > On Fri, 06 Nov 2015 10:41:16 +0100 David Kastrup <dak@gnu.org> wrote: 

   DK> I am not in a position to prescribe to Gnus developers how they
   DK> are maintaining their software. Maybe Gnus stopping to support
   DK> XEmacs 21.4 is the kick in the behind that XEmacs needs for
   DK> preparing a new "stable" release rather than face the prospect of
   DK> having to backport or freeze Gnus. But I don't know how receptive
   DK> to kicks that behind might be right now. For most active users,
   DK> XEmacs 21.4 does not appear to be more than a practical joke.

Sadly enough most debian based distribution still ship it instead of 
21.5.34 which is more decent.




  reply	other threads:[~2015-11-08 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151011210306.16935.15935@vcs.savannah.gnu.org>
     [not found] ` <E1ZlNlr-0004QG-3U@vcs.savannah.gnu.org>
2015-10-13  0:36   ` master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el Katsumi Yamaoka
2015-11-05 20:03     ` Ted Zlatanov
2015-11-06  2:22       ` Katsumi Yamaoka
2015-11-06  9:41         ` David Kastrup
2015-11-06 15:18         ` dropping support for old Emacsen (was: master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el) Ted Zlatanov
2015-11-08 15:33           ` Uwe Brauer [this message]
2015-11-06 21:40         ` master 644d31a 2/2: Replace the usage of an obsolete function in auth-source.el Richard Stallman
2015-11-06 22:48           ` David Kastrup
2015-11-07 13:26             ` Richard Stallman
2015-11-07 13:43               ` David Kastrup

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h9kwqze1.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).