From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: dports@macports.org, fgunbin@fastmail.fm, eggert@cs.ucla.edu,
bug-gnulib@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs 28.1 doesn't compile on Mac OS 10.7.5
Date: Sun, 17 Apr 2022 14:33:38 +0300 [thread overview]
Message-ID: <83zgkkx7u5.fsf@gnu.org> (raw)
In-Reply-To: <2BEDBEB3-8409-42B3-AF6C-1F18563A2CA2@acm.org> (message from Mattias Engdegård on Sun, 17 Apr 2022 11:13:43 +0200)
> Feedback-ID: mattiase@acm.or
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 17 Apr 2022 11:13:43 +0200
> Cc: dports@macports.org, Gnulib bugs <bug-gnulib@gnu.org>,
> Filipp Gunbin <fgunbin@fastmail.fm>, Emacs-Devel <emacs-devel@gnu.org>
>
> 17 apr. 2022 kl. 04.21 skrev Paul Eggert <eggert@cs.ucla.edu>:
> >
> > On 4/15/22 09:22, Mattias Engdegård wrote:
> >> Paul, would you consider something like that patch (repeated here) for gnulib?
> >
> > Sure, I installed the attached into Gnulib master on Savannah.
>
> Thank you! This particular change should be back-ported to emacs-28 once master has caught up with gnulib again.
If you are talking about a single change in lib/* files for this
particular problem, I'm fine with that. But synchronizing with Gnulib
on the release branch is out of the question, as that will bring too
many changes.
next prev parent reply other threads:[~2022-04-17 11:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 11:55 Emacs 28.1 doesn't compile on Mac OS 10.7.5 Werner LEMBERG
2022-04-15 13:16 ` Mattias Engdegård
2022-04-15 13:48 ` Mattias Engdegård
2022-04-15 15:23 ` Werner LEMBERG
2022-04-15 15:54 ` Eli Zaretskii
2022-04-15 16:48 ` Werner LEMBERG
2022-04-15 16:22 ` Mattias Engdegård
2022-04-15 16:41 ` Mattias Engdegård
2022-04-15 16:51 ` Werner LEMBERG
2022-04-15 17:13 ` Mattias Engdegård
2022-04-15 17:40 ` Werner LEMBERG
2022-04-15 18:34 ` Mattias Engdegård
2022-04-15 19:47 ` Eli Zaretskii
2022-04-16 5:18 ` Werner LEMBERG
2022-04-16 7:35 ` Werner LEMBERG
2022-04-16 10:30 ` Mattias Engdegård
2022-04-16 15:25 ` Werner LEMBERG
2022-04-17 2:21 ` Paul Eggert
2022-04-17 3:28 ` Jeffrey Walton
2022-04-17 7:54 ` Paul Eggert
2022-04-17 11:09 ` Werner LEMBERG
2022-04-17 14:33 ` Ryan Schmidt
2022-04-17 14:51 ` Jeffrey Walton
2022-04-17 9:13 ` Mattias Engdegård
2022-04-17 9:32 ` Po Lu
2022-04-17 9:38 ` Mattias Engdegård
2022-04-17 11:33 ` Eli Zaretskii [this message]
2022-04-17 12:27 ` Mattias Engdegård
2022-04-17 17:54 ` Paul Eggert
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=83zgkkx7u5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=dports@macports.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=mattiase@acm.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).