From: Ken Brown <kbrown@cornell.edu>
To: emacs-devel@gnu.org
Subject: Re: The emacs-28 release branch has been created
Date: Sat, 2 Oct 2021 21:35:36 -0400 [thread overview]
Message-ID: <6c7a9f1a-bf2d-4213-b954-2025eee1f282@cornell.edu> (raw)
In-Reply-To: <83lf3dgbl3.fsf@gnu.org>
On 9/30/2021 2:30 PM, Eli Zaretskii wrote:
> Barring any unexpected calamities, the first pretest of Emacs 28 will
> be produced from this branch in a few weeks' time.
I apologize in advance if this has already been answered somewhere, but I'm
curious how building from a pretest tarball will work for people who want to
test native compilation. Release tarballs always contain *.elc files, which
seem to inhibit the creation of the preloaded *.eln files.
I had assumed that commit 90655e4bc0 was intended to deal with this, but I'm not
able to see how it will work.
Thanks.
Ken
next prev parent reply other threads:[~2021-10-03 1:35 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 18:30 The emacs-28 release branch has been created Eli Zaretskii
2021-10-02 15:58 ` Windows Binaries Release: was The emacs-28 release branch Phillip Lord
2021-10-03 10:53 ` Po Lu
2021-10-04 19:04 ` Phillip Lord
2021-10-16 20:24 ` Konstantin Kharlamov
2021-10-17 0:43 ` Po Lu
2021-10-17 13:45 ` Konstantin Kharlamov
2021-10-20 15:26 ` Phillip Lord
2021-10-03 11:22 ` Corwin Brust
2021-10-04 19:05 ` Phillip Lord
2021-10-16 10:03 ` H. Dieter Wilhelm
2021-10-16 13:31 ` Corwin Brust
2021-10-16 16:01 ` H. Dieter Wilhelm
2021-10-20 15:24 ` Phillip Lord
2021-10-20 18:36 ` H. Dieter Wilhelm
2021-10-27 19:36 ` H. Dieter Wilhelm
2021-10-27 21:07 ` Phillip Lord
2021-11-01 20:47 ` H. Dieter Wilhelm
2021-11-01 21:06 ` Óscar Fuentes
2021-11-02 11:16 ` Eshell requires execute permission on Win10, was " H. Dieter Wilhelm
2021-11-02 14:37 ` Óscar Fuentes
2021-11-02 18:57 ` MinGW Sources, was: Windows Binaries Release H. Dieter Wilhelm
2021-11-02 19:07 ` Óscar Fuentes
2021-11-04 17:51 ` H. Dieter Wilhelm
2021-11-08 22:27 ` Phillip Lord
2021-11-09 12:25 ` Eli Zaretskii
2021-11-09 14:32 ` Phillip Lord
2021-11-02 10:47 ` Windows Binaries Release: was The emacs-28 release branch Phillip Lord
2021-11-02 12:05 ` H. Dieter Wilhelm
2021-10-20 15:16 ` Phillip Lord
2021-10-21 0:13 ` Corwin Brust
2021-10-27 21:11 ` Phillip Lord
2021-10-03 1:35 ` Ken Brown [this message]
2021-10-03 6:53 ` The emacs-28 release branch has been created Andreas Schwab
2021-10-03 9:27 ` Eli Zaretskii
2021-10-03 15:01 ` Ken Brown
2021-10-03 15:17 ` Eli Zaretskii
2021-10-03 15:34 ` Ken Brown
2021-10-03 16:11 ` Eli Zaretskii
2021-10-03 17:14 ` Ken Brown
2021-10-03 17:33 ` Eli Zaretskii
2021-10-03 17:49 ` Eli Zaretskii
2021-10-03 17:56 ` Ken Brown
2021-10-03 18:03 ` Eli Zaretskii
2021-10-03 19:20 ` Eli Zaretskii
2021-10-03 19:42 ` Eli Zaretskii
2021-10-03 19:45 ` Ken Brown
2021-10-03 21:21 ` Ken Brown
2021-10-03 22:40 ` Ken Brown
2021-10-04 18:51 ` Eli Zaretskii
2021-10-04 13:31 ` Ken Brown
2021-10-04 14:25 ` Eli Zaretskii
2021-10-04 14:39 ` Eli Zaretskii
2021-10-04 14:45 ` Andrea Corallo via Emacs development discussions.
2021-10-04 14:54 ` Eli Zaretskii
2021-10-04 15:13 ` Andrea Corallo via Emacs development discussions.
2021-10-04 16:15 ` Andrea Corallo via Emacs development discussions.
2021-10-04 16:58 ` Eli Zaretskii
2021-10-04 19:38 ` Andrea Corallo via Emacs development discussions.
2021-10-04 19:40 ` Andrea Corallo via Emacs development discussions.
2021-10-04 19:54 ` Eli Zaretskii
2021-10-04 21:58 ` Ken Brown
2021-10-05 11:43 ` Eli Zaretskii
2021-10-05 15:43 ` Andrea Corallo via Emacs development discussions.
2021-10-05 11:29 ` Eli Zaretskii
2021-10-05 15:37 ` Andrea Corallo via Emacs development discussions.
2021-10-05 16:14 ` Eli Zaretskii
2021-10-05 16:52 ` Andrea Corallo via Emacs development discussions.
2021-10-05 17:12 ` Eli Zaretskii
2021-10-04 11:37 ` Eli Zaretskii
2021-10-04 13:11 ` Ken Brown
2021-10-04 13:34 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c7a9f1a-bf2d-4213-b954-2025eee1f282@cornell.edu \
--to=kbrown@cornell.edu \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.