From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Noam Postavsky <npostavs@gmail.com>, emacs-devel@gnu.org
Subject: Re: Declaring cl.el obsolete
Date: Fri, 24 May 2019 10:28:03 -0400 [thread overview]
Message-ID: <jwvv9y02aqd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <831s0p6ym9.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 May 2019 17:20:46 +0300")
>> > Maybe we should do this more gradually, like first deprecate it and
>> > print some kind of warning for it?
>> Isn't that what moving to lisp/obsolete/ does?
> Maybe.
I don't understand this "Maybe".
Moving a package to lisp/obsolete (which always comes with an
announcement in etc/NEWS) does two things, AFAICT:
- announce that this package is officially deprecated.
- cause a warning to be emitted when the package is used.
IOW exactly what you say we should do "first", except maybe that we use
the term "obsoleted" instead of "deprecated". So is the specific word
the source of your doubt?
Stefan
next prev parent reply other threads:[~2019-05-24 14:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 3:26 Declaring cl.el obsolete Stefan Monnier
2019-05-23 4:47 ` Eli Zaretskii
2019-05-23 10:28 ` Noam Postavsky
2019-05-23 14:20 ` Eli Zaretskii
2019-05-24 14:28 ` Stefan Monnier [this message]
2019-05-24 15:03 ` Eli Zaretskii
2019-05-24 16:22 ` Stefan Monnier
2019-05-23 8:44 ` Lars Ingebrigtsen
2019-05-23 8:50 ` Lars Ingebrigtsen
2019-05-23 17:03 ` Romanos Skiadas
2019-05-24 1:22 ` 조성빈
2019-05-25 20:12 ` Romanos Skiadas
2019-05-23 12:15 ` Stefan Monnier
2019-05-23 15:08 ` Ken Olum
2019-05-23 15:57 ` Sam Steingold
2019-07-23 15:07 ` Stefan Monnier
2019-07-23 16:29 ` Drew Adams
2019-07-23 16:55 ` Stefan Monnier
2019-08-06 8:02 ` Stefan Monnier
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=jwvv9y02aqd.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
/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).