From: Po Lu <luangruo@yahoo.com>
To: Platon Pronko <platon7pronko@gmail.com>
Cc: Lloyd Zusman <hippoman@potamuses.net>, help-gnu-emacs@gnu.org
Subject: Re: Changes to `make-obsolete` and similar functions make upgrades nearly impossible.
Date: Mon, 24 Apr 2023 14:59:02 +0800 [thread overview]
Message-ID: <87bkjdepft.fsf@yahoo.com> (raw)
In-Reply-To: <7e85ff18-09c7-f02d-0226-e16aa272802f@gmail.com> (Platon Pronko's message of "Mon, 24 Apr 2023 14:24:08 +0800")
Platon Pronko <platon7pronko@gmail.com> writes:
> Even the 23.1 release should compile and run fine today.
This is, alas, no longer true. Nothing prior to Emacs 27.1 compiles and
runs correctly on a recent GNU/Linux system.
It is possible to make 23.x work again -- several people currently use a
modified 23.4, but the changes have not been made public.
next prev parent reply other threads:[~2023-04-24 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 13:56 Changes to `make-obsolete` and similar functions make upgrades nearly impossible Lloyd Zusman
2023-04-24 6:24 ` Platon Pronko
2023-04-24 6:59 ` Po Lu [this message]
2023-04-24 7:37 ` Platon Pronko
2023-04-25 15:34 ` Ruijie Yu via Users list for the GNU Emacs text editor
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=87bkjdepft.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
--cc=hippoman@potamuses.net \
--cc=platon7pronko@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.
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).