From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.3 released
Date: Wed, 27 Mar 2024 00:54:59 -0500 [thread overview]
Message-ID: <CAJf-WoQ222ZuZ0izu4ssJpLz3Br8OCqm4hMsM6FKw0E8Jxx60A@mail.gmail.com> (raw)
In-Reply-To: <86ttkvjtvo.fsf@gnu.org>
On Sun, Mar 24, 2024 at 2:46 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Corwin Brust <corwin@bru.st>
> > Date: Sun, 24 Mar 2024 14:36:08 -0500
> > I'm inclined to go ahead and publish using the version where I run
> > autogen.sh -- let me know if we prefer that we track this issue down
> > first, instead.
>
> I don't think autogen.sh can do any harm, but I cannot be sure without
> understanding why you see this weird problem.
>
Windows binaries for 29.3 are now pushed. Please let me know if you hit snags.
https://ftpmirror.gnu.org/gnu/emacs/windows/emacs-29/?C=M;O=D
I will continue trying to figure out what I ran into here, replying
next to your question/suggestion down thread.
Meanwhile, I didn't want people who might be waiting for these
binaries to upgrade a work computer or something to wait any longer.
Many thanks to libera.chat user IsoLinCHiP for help testing this
round, especially as this caught a problem I'd missed with the fullzip
and installer in the first set I made, yesterday. (I inadvertently
picked up libgccjit when packing DLLs to include, meaning there are
still issues with my patches for build-dep-zips.py.)
next prev parent reply other threads:[~2024-03-27 5:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 14:14 Emacs 29.3 released Eli Zaretskii
2024-03-24 17:52 ` Corwin Brust
2024-03-24 18:46 ` Eli Zaretskii
2024-03-24 19:36 ` Corwin Brust
2024-03-24 19:46 ` Eli Zaretskii
2024-03-24 19:58 ` Eli Zaretskii
2024-03-27 5:54 ` Corwin Brust [this message]
2024-03-24 18:48 ` Michael Albinus
2024-03-24 19:29 ` Eli Zaretskii
2024-03-24 20:10 ` Michael Albinus
2024-03-24 20:20 ` Eli Zaretskii
2024-03-26 8:48 ` Michael Albinus
2024-03-26 12:46 ` Eli Zaretskii
2024-03-26 14:28 ` Michael Albinus
2024-03-26 14:38 ` Ihor Radchenko
2024-03-26 17:50 ` Michael Albinus
2024-03-26 18:01 ` Ihor Radchenko
2024-03-26 18:48 ` Michael Albinus
2024-03-26 19:35 ` Eli Zaretskii
2024-03-27 8:27 ` Michael Albinus
2024-03-27 12:42 ` Eli Zaretskii
2024-03-27 14:07 ` Michael Albinus
2024-03-27 16:42 ` Eli Zaretskii
2024-03-27 17:35 ` Michael Albinus
2024-04-03 12:03 ` Michael Albinus
2024-04-03 12:36 ` Robert Pluim
2024-04-03 15:01 ` Michael Albinus
2024-04-03 12:51 ` Eli Zaretskii
2024-04-03 14:56 ` Michael Albinus
2024-04-04 12:25 ` Eli Zaretskii
2024-04-04 12:40 ` Michael Albinus
2024-04-04 17:46 ` Ihor Radchenko
2024-03-27 15:15 ` Corwin Brust
2024-03-26 15:32 ` Ulrich Mueller
2024-03-26 18:42 ` Michael Albinus
2024-04-06 15:45 ` Lynn Winebarger
2024-04-06 16:09 ` 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
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=CAJf-WoQ222ZuZ0izu4ssJpLz3Br8OCqm4hMsM6FKw0E8Jxx60A@mail.gmail.com \
--to=corwin@bru.st \
--cc=eliz@gnu.org \
--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 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).