From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bzg@gnu.org, larsi@gnus.org, emacs-devel@gnu.org,
yantar92@gmail.com, kyle@kyleam.com
Subject: Re: Tentative release schedule for Emacs 29.1
Date: Wed, 16 Nov 2022 21:26:57 +0800 [thread overview]
Message-ID: <87cz9nhvxa.fsf@yahoo.com> (raw)
In-Reply-To: <83iljfgi14.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Nov 2022 15:12:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> We will not release Emacs 29.1 with that bug, that's for sure. But I
> don't want to wait for its solution before cutting the release branch,
> since we can continue working on it after the branching.
OK, thanks, I thought might not have been okay to do that after the
branch was cut.
BTW, that means I can keep fixing regressions from Emacs 28 in the X
code, right? There may still be problems with obscure input devices
which used to work with the core input code, but need special treatment
on XI2.
> If your crashes are like the one reported there, how about if you
> disable mouse-highlight as a temporary workaround?
I'll try that and see if that makes it better.
next prev parent reply other threads:[~2022-11-16 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:03 Tentative release schedule for Emacs 29.1 Lars Ingebrigtsen
2022-09-24 6:44 ` Bastien
2022-09-24 10:32 ` Lars Ingebrigtsen
2022-09-24 16:24 ` Bastien
2022-11-16 4:43 ` Bastien
2022-11-16 4:52 ` Po Lu
2022-11-16 13:12 ` Eli Zaretskii
2022-11-16 13:26 ` Po Lu [this message]
2022-11-16 13:52 ` Eli Zaretskii
2022-11-16 13:51 ` Stefan Monnier
2022-11-16 13:59 ` Eli Zaretskii
2022-11-16 13:09 ` Eli Zaretskii
2022-11-16 13:23 ` Bastien
2022-11-16 13:50 ` Eli Zaretskii
2022-11-16 14:53 ` Bastien
2022-11-16 16:45 ` 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=87cz9nhvxa.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=bzg@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=larsi@gnus.org \
--cc=yantar92@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).