From: Alan Third <alan@idiocy.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
obriendavid1@gmail.com, me@eshelyaron.com, 63495@debbugs.gnu.org,
mardani29@yahoo.es
Subject: bug#63495: 28.2; menu crashes on macos
Date: Wed, 6 Sep 2023 21:29:32 +0100 [thread overview]
Message-ID: <ZPjhLK14eCgjwMiQ@idiocy.org> (raw)
In-Reply-To: <CADwFkmnax8NXdiOo+K-Ch8FjN8K_=kQ2bZPLccyg_+4SUEbr7g@mail.gmail.com>
On Wed, Sep 06, 2023 at 01:16:07PM -0700, Stefan Kangas wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Cc: 63495@debbugs.gnu.org, obriendavid1@gmail.com, me@eshelyaron.com
> >> Date: Tue, 25 Jul 2023 17:16:17 +0100
> >> From: Alan Third <alan@idiocy.org>
> >>
> >> If it hasn't already, this should probably be pushed into the emacs-29
> >> branch, unless someone's noticed a problem with it, as I understand
> >> the first(?) rc has already been released.
> >
> > RC1 is not a "release", it's a tentative release. The release itself
> > will happen a few days from now, fingers crossed.
> >
> >> This fixes a crash.
> >>
> >> Eli/Lars? Is it too late?
> >
> > Too late for Emacs 29.1, yes. Unless a much more serious catastrophe
> > will be uncovered soon, in which case I will have to make one more
> > pretest.
>
> Would it make sense to install it on the emacs-29 now? I don't see it
> installed on master either.
I think so.
I had assumed Daniel would have pushed it, since it was his patch, so
I didn't follow up on it.
--
Alan Third
next prev parent reply other threads:[~2023-09-06 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 15:36 bug#63495: 28.2; menu crashes on macos David O'Brien
2023-05-14 9:18 ` Eli Zaretskii
2023-07-08 18:18 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 7:29 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10 21:00 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10 22:33 ` Alan Third
2023-07-11 5:40 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-12 17:25 ` Alan Third
2023-07-12 17:44 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-12 19:37 ` Alan Third
2023-07-13 6:16 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 8:47 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 19:41 ` Alan Third
2023-07-25 16:16 ` Alan Third
2023-07-25 17:47 ` Eli Zaretskii
2023-09-06 20:16 ` Stefan Kangas
2023-09-06 20:29 ` Alan Third [this message]
2023-09-06 22:34 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-07 5:23 ` 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=ZPjhLK14eCgjwMiQ@idiocy.org \
--to=alan@idiocy.org \
--cc=63495@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mardani29@yahoo.es \
--cc=me@eshelyaron.com \
--cc=obriendavid1@gmail.com \
--cc=stefankangas@gmail.com \
/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).