unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: emacs-devel@gnu.org
Subject: Some native compiler related renaming
Date: Thu, 06 May 2021 15:17:22 +0000	[thread overview]
Message-ID: <xjfy2crsxh9.fsf@sdf.org> (raw)

Hi all,

just to mention that as suggested in bug#48025 I've pushed a bunch of
commits to perform the following renamings:

comp-eln-load-path → native-comp-eln-load-path
comp-warning-on-missing-source -> native-comp-warning-on-missing-source
comp-native-driver-options → native-comp-driver-options
comp-async-query-on-exit → native-comp-async-query-on-exit
comp-async-report-warnings-errors -> native-comp-async-report-warnings-errors
comp-async-env-modifier-form → native-comp-async-env-modifier-form
comp-async-all-done-hook → native-comp-async-all-done-hook
comp-async-cu-done-functions → native-comp-async-cu-done-functions
comp-async-jobs-number → native-comp-async-jobs-number
comp-never-optimize-functions → native-comp-never-optimize-functions
comp-bootstrap-deny-list → native-comp-bootstrap-deny-list
comp-always-compile → native-comp-always-compile
comp-verbose -> native-comp-verbose
comp-debug -> native-comp-debug
comp-speed -> native-comp-speed
comp-limple-mode -> native-comp-limple-mode

Hopefully I'm not creating too much breakage.

Regards

  Andrea



             reply	other threads:[~2021-05-06 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 15:17 Andrea Corallo via Emacs development discussions. [this message]
2021-05-08 13:30 ` Some native compiler related renaming Eli Zaretskii
2021-05-08 15:03   ` Basil L. Contovounesios
2021-05-08 15:50     ` Eli Zaretskii
2021-05-08 17:01       ` Basil L. Contovounesios
2021-05-08 21:28   ` Alan Mackenzie
2021-05-09  6:49     ` Eli Zaretskii
2021-05-10  7:42   ` Andrea Corallo via Emacs development discussions.
2021-05-11  8:40   ` Andrea Corallo via Emacs development discussions.
2021-05-11 12:26     ` Eli Zaretskii
2021-05-11 16:33       ` Andrea Corallo via Emacs development discussions.

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=xjfy2crsxh9.fsf@sdf.org \
    --to=emacs-devel@gnu.org \
    --cc=akrl@sdf.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).