From: Richard Stallman <rms@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: eliz@gnu.org, sds@gnu.org, emacs-devel@gnu.org
Subject: Re: when do we remove backward compatibility definitions?
Date: Wed, 22 Nov 2017 17:54:57 -0500 [thread overview]
Message-ID: <E1eHduz-0000oI-F0@fencepost.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)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> For platform issues (old
> POSIX platforms that don't support newer POSIX features, for example),
> the general rule of thumb I use in Emacs and elsewhere is, "If the
> platform's supplier no longer supports the platform, then Emacs doesn't
> need to worry about supporting it either."
I think that as long as users of the platform want to do the work
to keep supporting it, we should give them the necessary cooperation.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
prev parent reply other threads:[~2017-11-22 22:54 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
2017-11-22 15:48 ` Eli Zaretskii
2017-11-22 3:27 ` Eli Zaretskii
2017-11-22 22:54 ` Richard Stallman [this message]
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=E1eHduz-0000oI-F0@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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.