From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: owinebar@gmail.com, stephen_leake@stephe-leake.org,
emacs-devel@gnu.org, Stromeko@nexgo.de
Subject: Re: disable automatic native-compilation?
Date: Mon, 11 Jul 2022 16:56:56 +0300 [thread overview]
Message-ID: <83o7xvzr9z.fsf@gnu.org> (raw)
In-Reply-To: <a011a1d3-51fc-9d7a-d8ea-3d1f205694c1@cornell.edu> (message from Ken Brown on Mon, 11 Jul 2022 09:37:35 -0400)
> Date: Mon, 11 Jul 2022 09:37:35 -0400
> Cc: Eli Zaretskii <eliz@gnu.org>,
> Stephen Leake <stephen_leake@stephe-leake.org>,
> emacs-devel <emacs-devel@gnu.org>, Achim Gratz <Stromeko@nexgo.de>
> From: Ken Brown <kbrown@cornell.edu>
>
> > Will do, but could you include the details of the announcement in the emacs
> > source distribution somewhere, as is done for the other variants with specific
> > instructions? I'm only incidentally building it in a cygwin environment - it
> > didn't even occur to me to check the general cygwin mailing list.
>
> Yes, I'll add something to etc/PROBLEMS unless you or Eli can suggest a better
> place.
PROBLEMS is fine for this kind of information. But please add that to
the release branch, as it is relevant to Emacs 28.
Thanks.
next prev parent reply other threads:[~2022-07-11 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 16:49 disable automatic native-compilation? Stephen Leake
2022-07-09 17:23 ` Eli Zaretskii
2022-07-10 15:10 ` Lynn Winebarger
2022-07-10 15:39 ` Eli Zaretskii
2022-07-10 18:32 ` Lynn Winebarger
2022-07-10 21:54 ` Ken Brown
2022-07-11 1:52 ` Ken Brown
2022-07-11 2:39 ` Lynn Winebarger
2022-07-11 13:37 ` Ken Brown
2022-07-11 13:56 ` Eli Zaretskii [this message]
2022-07-11 17:19 ` Ken Brown
2022-07-09 22:36 ` Tor Kringeland
2022-07-10 8:58 ` Philip Kaludercic
2022-07-11 12:54 ` Andrea Corallo
2022-07-12 11:04 ` Tor Kringeland
2022-07-12 11:27 ` Tor Kringeland
2022-07-12 13:29 ` Eli Zaretskii
2022-08-06 15:32 ` Lynn Winebarger
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=83o7xvzr9z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--cc=owinebar@gmail.com \
--cc=stephen_leake@stephe-leake.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).