Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Emacs 20.7 compatibility in v5-10
Date: Thu, 13 Apr 2006 19:45:07 +0200	[thread overview]
Message-ID: <v9k69tid3w.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3bqv5ig4z.fsf@quimbies.gnus.org>

On Thu, Apr 13 2006, Lars Magne Ingebrigtsen wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> But actually I was aiming in the opposite direction...
>
> Sure; just drop Emacs 20 support for 5.10 as well.

Done[1].  Also for XEmacs 21.1 (the XEmacs maintainers have stopped
supporting in some years ago).

Do you suggest to rip out Emacs 20/XEmacs 21.1 stuff systematically
like it was done after the start of No Gnus (mostly by Jesper and
Katsumi [2]) or only drop it on occasion?

Bye, Reiner.

[1]
--8<---------------cut here---------------start------------->8---
--- gnus.texi	11 Apr 2006 16:12:41 +0200	6.603.2.82
+++ gnus.texi	13 Apr 2006 19:29:32 +0200	
@@ -24870,16 +24870,17 @@
 @itemize @bullet
 
 @item
-Emacs 20.7 and up.
+Emacs 21.1 and up.
 
 @item
-XEmacs 21.1 and up.
+XEmacs 21.4 and up.
 
 @end itemize
 
 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.
+Emacs versions.  Particularly, Gnus 5.10.8 should also work on Emacs
+20.7 and XEmacs 21.1.
 
 There are some vague differences between Gnus on the various
 platforms---XEmacs features more graphics (a logo and a toolbar)---but
--8<---------------cut here---------------end--------------->8---

[2]
--8<---------------cut here---------------start------------->8---
7 matches for "Emacs 20\|XEmacs 21.1" in buffer: ChangeLog
   3278:	which Emacs 20 doesn't support.
   7882:	* gnus-util.el (gnus-replace-in-string): Remove Emacs 20 code.
   8098:	* dgnushack.el: Remove some XEmacs 21.1 specific stuff.
   8154:	* gnus-registry.el: Remove Emacs 20 hash table compatibility code.
   8218:	Remove Emacs 20 hash table compatibility code.
   8245:	Remove Emacs 20 stuff:
   8252:	Emacs 20.
--8<---------------cut here---------------end--------------->8---
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2006-04-13 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 10:43 Improve handling of message/external-body Katsumi Yamaoka
2006-04-12  2:01 ` Katsumi Yamaoka
2006-04-12 12:49   ` rfc2231.el changes (was: Improve handling of message/external-body) Reiner Steib
2006-04-13  0:37     ` rfc2231.el changes Katsumi Yamaoka
2006-04-13  5:45       ` Lars Magne Ingebrigtsen
2006-04-13 16:25         ` Emacs 20.7 compatibility in v5-10 (was: rfc2231.el changes) Reiner Steib
2006-04-13 16:39           ` Emacs 20.7 compatibility in v5-10 Lars Magne Ingebrigtsen
2006-04-13 17:45             ` Reiner Steib [this message]
2006-04-13 18:31               ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 20:59 Gnus manual update Chong Yidong
2006-02-06 19:18 ` Ted Zlatanov
2006-02-06 20:19   ` Chong Yidong
2006-02-06 20:31     ` spam manual update for Gnus (was: Gnus manual update) Ted Zlatanov
2006-02-06 22:49       ` spam manual update for Gnus Reiner Steib
2006-02-08 20:20         ` Ted Zlatanov
2006-02-09 15:00           ` spam.el: Bugs, compatibility with v5-10 (was: spam manual update for Gnus) Reiner Steib
2006-02-13 19:04             ` spam.el: Bugs, compatibility with v5-10 Ted Zlatanov
2006-02-13 22:36               ` Emacs 20.7 compatibility in v5-10 (was: spam.el: Bugs, compatibility with v5-10) Reiner Steib
2006-03-20 19:51                 ` Emacs 20.7 compatibility in v5-10 Ted Zlatanov
2006-03-20 20:38                   ` 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=v9k69tid3w.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).