From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Fleischer <daniel.fleischer@amobee.com>,
Alan Third <alan@idiocy.org>
Cc: 50411@debbugs.gnu.org, nisoni@algon.dk, danflscr@gmail.com
Subject: bug#50411: 28.0.50; emacs compilation
Date: Sun, 19 Sep 2021 19:16:57 +0300 [thread overview]
Message-ID: <83bl4o4k1y.fsf@gnu.org> (raw)
In-Reply-To: <m28rzswsbz.fsf@amobee.com> (message from Daniel Fleischer on Sun, 19 Sep 2021 17:30:40 +0300)
> From: Daniel Fleischer <daniel.fleischer@amobee.com>
> Cc: Daniel Fleischer <danflscr@gmail.com>, 50411@debbugs.gnu.org,
> nisoni@algon.dk
> Date: Sun, 19 Sep 2021 17:30:40 +0300
>
> Eli Zaretskii [2021-09-19 Sun 08:40] wrote:
>
> > Thanks, this LGTM, but could you also include in the entry the
> > indications of the problem which this fixes? PROBLEMS is supposed to
> > be searched for error messages and other problematic indications users
> > see when they build or use Emacs.
>
> Attached.
Thanks, this LGTM. Let's wait for a while to see whether we need to
say something about this being specific to Intel CPUs. Also, I'd like
Alan (CC'ed) to okay this.
next prev parent reply other threads:[~2021-09-19 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 19:10 bug#50411: 28.0.50; emacs compilation Niels Søndergaard
2021-09-06 4:39 ` Eli Zaretskii
2021-09-06 8:30 ` Niels Søndergaard
2021-09-06 8:38 ` Niels Søndergaard
2021-09-06 10:58 ` Eli Zaretskii
2021-09-18 13:58 ` Daniel Fleischer
2021-09-18 14:20 ` Eli Zaretskii
2021-09-18 20:28 ` Niels Søndergaard
2021-09-18 21:25 ` Daniel Fleischer
2021-09-19 0:46 ` Niels Søndergaard
2021-09-19 7:08 ` Daniel Fleischer
2021-09-19 5:40 ` Eli Zaretskii
2021-09-19 14:30 ` Daniel Fleischer
2021-09-19 16:16 ` Eli Zaretskii [this message]
2021-09-19 17:56 ` Alan Third
2021-09-22 6:49 ` Eli Zaretskii
2021-09-22 7:09 ` Niels Søndergaard
2022-08-22 20:50 ` Lars Ingebrigtsen
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=83bl4o4k1y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50411@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=danflscr@gmail.com \
--cc=daniel.fleischer@amobee.com \
--cc=nisoni@algon.dk \
/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).