From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: when do we remove backward compatibility definitions?
Date: Tue, 21 Nov 2017 12:37:13 -0500 [thread overview]
Message-ID: <lzvai3ildi.fsf@gnu.org> (raw)
In-Reply-To: lztvycsow9.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
Hi,
I asked this question 3 weeks ago and got no replies:
> * Sam Steingold <fqf@tah.bet> [2017-11-02 11:04:22 -0400]:
>
> Gnus has a few backward compatibility face declarations like this:
>
> (put 'gnus-group-news-4-face 'obsolete-face "22.1")
>
> Emacs 22.1 was released on 2007-06-02 -- over 10 years ago.
>
> What is the policy on removing such declarations?
>
> R releases?
> M major releases?
> Y years?
>
> Where is it officially documented?
To salivate our thinking, here are the obsolescence annotations in the
lisp sources (the code is attached):
--8<---------------cut here---------------start------------->8---
(insert-counter-alist
(counter-table-to-sorted-alist
(second (elof-count-all-obsolete "..../emacs/trunk/lisp"))))
25.1 193
22.1 172
24.3 127
24.1 125
24.4 123
23.1 88
26.1 65
Org 9.0 63
23.2 32
Org 9.1 15
Emacs 24.1 7
23.3 7
24.5 7
Gnus 5.10.9 (Emacs 22.1) 6
23.4 5
22.2 5
ERC 5.1 4
27.1 4
21.1 4
Gnus 5.10 (Emacs 22.1) 2
Emacs 22.1 2
Emacs 23.1 2
Org 8.2 2
Org 8.3 2
speedbar 1.0pre3 (Emacs 23.1) 2
rst 1.0.0 2
icalendar 0.19 1
CEDET 1.1 1
Emacs 26.1 1
20.3 1
Gnus 5.9 (Emacs 22.1) 1
19.34 1
2011-08-02 1
CC Mode 5.31.4, 2006-04-14 1
at least 19.34 1
before 19.34 1
25.2 1
--8<---------------cut here---------------end--------------->8---
It does look like GNU Emacs 22.1 (2007-06-02) is a good cut-off candidate.
[-- Attachment #2: Find Emacs Lisp obsolete forms. --]
[-- Type: application/emacs-lisp, Size: 2596 bytes --]
[-- Attachment #3: Type: text/plain, Size: 279 bytes --]
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://think-israel.org https://jihadwatch.org http://www.dhimmitude.org
WinWord 6.0 UNinstall: Not enough disk space to uninstall WinWord
next prev parent reply other threads:[~2017-11-21 17:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 15:04 when do we remove backward compatibility definitions? Sam Steingold
2017-11-21 17:37 ` Sam Steingold [this message]
2017-11-21 19:54 ` Paul Eggert
2017-11-21 20:03 ` Eli Zaretskii
2017-11-21 20:18 ` Paul Eggert
2017-11-21 20:36 ` Eli Zaretskii
2017-11-21 21:07 ` Sam Steingold
2017-11-21 21:14 ` Paul Eggert
2017-11-21 21:57 ` Sam Steingold
2017-11-22 3:30 ` Eli Zaretskii
2017-11-22 7:15 ` Paul Eggert
2017-11-22 15:48 ` Eli Zaretskii
2017-11-22 3:27 ` Eli Zaretskii
2017-11-22 22:54 ` Richard Stallman
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=lzvai3ildi.fsf@gnu.org \
--to=sds@gnu.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).