unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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:03:13 +0200	[thread overview]
Message-ID: <834lpncsce.fsf@gnu.org> (raw)
In-Reply-To: <b362b68b-9350-0aa8-03da-7196a0f79fb9@cs.ucla.edu> (message from Paul Eggert on Tue, 21 Nov 2017 11:54:13 -0800)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 21 Nov 2017 11:54:13 -0800
> 
> > R releases?
> > M major releases?
> > Y years?
> >
> > Where is it officially documented?
> 
> I don't think we have an official policy, so how about this as a first 
> cut: If the oldest GNU/Linux or other GNU distribution still in 
> reasonably widespread use has Emacs version N, then we don't need to 
> continue to support features that were marked obsolete in version N or 
> earlier.

No, I don't think we should look at GNU/Linux distributions to
determine such a policy.  Emacs is a separate project, and shouldn't
depend on any OS distributions.

And I'm not even sure we should have a policy.  For starters, who will
implement it?

Let's instead solve practical problems with such issues.  Are there
any practical problems here?  If so, what are they?

Thanks.



  reply	other threads:[~2017-11-21 20:03 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 [this message]
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=834lpncsce.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 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).