From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: sds@gnu.org, emacs-devel@gnu.org
Subject: Re: when do we remove backward compatibility definitions?
Date: Tue, 21 Nov 2017 22:36:16 +0200 [thread overview]
Message-ID: <831skrcqtb.fsf@gnu.org> (raw)
In-Reply-To: <cfcf3748-7ae0-c045-f2c5-2361f5700cdf@cs.ucla.edu> (message from Paul Eggert on Tue, 21 Nov 2017 12:18:41 -0800)
> Cc: sds@gnu.org, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 21 Nov 2017 12:18:41 -0800
>
> On 11/21/2017 12:03 PM, Eli Zaretskii wrote:
> > Let's instead solve practical problems with such issues. Are there
> > any practical problems here? If so, what are they?
>
> The practical problem is that when we have cruft in the Emacs source
> code that makes maintenance harder
No, we don't have any cruft, not from my POV.
> My attempt at writing a guideline for supporting obsolete Emacs features
> is intended to be along similar lines. It is not meant to be
> prescriptive and so I shouldn't have used the word "policy" to describe
> it. It is merely meant as a common-sense guideline for when Emacs
> features are so obsolete that they can be removed if that simplifies
> maintenance.
Sorry, I'm not interested in discussing abstract policies that have no
specific problems behind them. It's a waste of our time. If there is
a specific problem with the variables Sam saw, let's discuss those
instead.
next prev parent reply other threads:[~2017-11-21 20:36 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831skrcqtb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.