From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 48221@debbugs.gnu.org
Subject: bug#48221: 28.0.50; defsubsts aren't native compiled?
Date: Wed, 05 May 2021 20:33:49 +0000 [thread overview]
Message-ID: <xjfim3wudhu.fsf@sdf.org> (raw)
In-Reply-To: <83eeel2mfv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 May 2021 19:08:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: larsi@gnus.org, 48221@debbugs.gnu.org
>> Date: Wed, 05 May 2021 15:23:47 +0000
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> Date: Wed, 05 May 2021 18:10:58 +0300
>> >> From: Eli Zaretskii <eliz@gnu.org>
>> >> Cc: larsi@gnus.org, 48221@debbugs.gnu.org
>> >>
>> >> Thanks. I think the feature should be renamed to native-comp
>> >
>> > Sorry, I meant native-compile.
>>
>> NP, BTW in the configure we use `native-compilation' shouldn't we use
>> this?
>
> I thought native-compile was better because we talked about renaming a
> bunch of variables to have that prefix, so it would be consistent.
Okay, I've the impression we all agreed on native-compile for the
feature name so I did the renaming with 40736357b8. The configure flag
in any case is a different subject.
Thanks
Andrea
next prev parent reply other threads:[~2021-05-05 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 9:59 bug#48221: 28.0.50; defsubsts aren't native compiled? Lars Ingebrigtsen
2021-05-04 16:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 9:36 ` Lars Ingebrigtsen
2021-05-05 14:57 ` Eli Zaretskii
2021-05-05 14:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 15:03 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 15:10 ` Eli Zaretskii
2021-05-05 15:13 ` Eli Zaretskii
2021-05-05 15:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 15:31 ` Lars Ingebrigtsen
2021-05-05 15:46 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 16:09 ` Eli Zaretskii
2021-05-05 16:08 ` Eli Zaretskii
2021-05-05 20:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-06 4:49 ` Eli Zaretskii
2021-05-06 7:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 8:09 ` Eli Zaretskii
2021-05-05 15:00 ` Lars Ingebrigtsen
2021-05-05 15:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-05 15:21 ` 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=xjfim3wudhu.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48221@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).