unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Sam Steingold <sds@gnu.org>
Cc: Emacs Development <Emacs-devel@gnu.org>
Subject: Re: when do we remove backward compatibility definitions?
Date: Tue, 21 Nov 2017 23:15:03 -0800	[thread overview]
Message-ID: <4558a0a5-4253-005c-e8e7-b9a1b99d2bee@cs.ucla.edu> (raw)
In-Reply-To: <lzefori9c3.fsf@gnu.org>

Sam Steingold wrote:
> these seem clear-cut:
> 
> mail/sendmail.el:(make-obsolete-variable 'mail-yank-hooks 'mail-citation-hook "19.34")
> mh-e/mh-letter.el(mh-make-obsolete-variable 'mh-yank-hooks 'mail-citation-hook "19.34")

Yes, removing those makes sense.

> these are more controversial:
> 
> select.el:
> ;; Only declared obsolete in 23.3.
> (define-obsolete-function-alias 'x-selection 'x-get-selection "at least 19.34")

Since this wasn't declared obsolete until 23.3 and 23.1 is still used enough, 
I'd leave it in for now.

> subr.el:
> ;; Lisp manual only updated in 22.1.
> (define-obsolete-variable-alias 'executing-macro 'executing-kbd-macro
>    "before 19.34")

22.1 is old enough so that alias can go, if you ask me.



  parent reply	other threads:[~2017-11-22  7:15 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
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 [this message]
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=4558a0a5-4253-005c-e8e7-b9a1b99d2bee@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=Emacs-devel@gnu.org \
    --cc=sds@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).