From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Gregory Heytings <gregory@heytings.org>,
Emacs developers <emacs-devel@gnu.org>,
Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: emacs.pdmp not always rebuilt
Date: Mon, 4 Oct 2021 13:14:02 +0200 [thread overview]
Message-ID: <CADwFkmmfeQ4=PiPNAG8a596UXksvVm45Mfjta7kBT6Q1D71nLw@mail.gmail.com> (raw)
In-Reply-To: <87mtnpp2p5.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> If there are no reported issues with this, perhaps it should be
> cherry-picked for emacs-28?
FWIW, I think that would make sense; in many cases the change won't
matter and it fixes a real problem.
If someone is parsing the build output and are looking for markers
produced by 'substitute-command-keys', I guess they might have a
problem, but that seems minor in comparison to the issue this solves.
next prev parent reply other threads:[~2021-10-04 11:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 12:41 emacs.pdmp not always rebuilt Lars Ingebrigtsen
2021-10-03 12:53 ` Eli Zaretskii
2021-10-03 13:10 ` Lars Ingebrigtsen
2021-10-03 14:35 ` Stefan Monnier
2021-10-03 14:38 ` Lars Ingebrigtsen
2021-10-03 23:27 ` Gregory Heytings
2021-10-04 0:45 ` Stefan Kangas
2021-10-04 2:28 ` Eli Zaretskii
2021-10-04 8:57 ` Gregory Heytings
2021-10-04 9:19 ` Lars Ingebrigtsen
2021-10-04 11:14 ` Stefan Kangas [this message]
2021-10-04 12:53 ` Eli Zaretskii
2021-10-04 12:50 ` Eli Zaretskii
2021-10-04 13:05 ` Gregory Heytings
2021-10-04 13:25 ` Gregory Heytings
2021-10-04 13:37 ` Eli Zaretskii
2021-10-04 14:18 ` Gregory Heytings
2021-10-04 14:34 ` Eli Zaretskii
2021-10-04 16:02 ` Gregory Heytings
2021-10-04 16:56 ` Eli Zaretskii
2021-10-04 13:30 ` Eli Zaretskii
2021-10-04 14:03 ` Stefan Kangas
2021-10-04 14:19 ` Gregory Heytings
2021-10-04 15:10 ` Eli Zaretskii
2021-10-03 14:52 ` Eli Zaretskii
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='CADwFkmmfeQ4=PiPNAG8a596UXksvVm45Mfjta7kBT6Q1D71nLw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).