From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 29.2 released
Date: Sat, 20 Jan 2024 08:51:10 +0200 [thread overview]
Message-ID: <83cytwv6ox.fsf@gnu.org> (raw)
In-Reply-To: <87le8lkohx.fsf@gmx.de> (message from Michael Albinus on Fri, 19 Jan 2024 22:22:02 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: emacs-devel@gnu.org
> Date: Fri, 19 Jan 2024 22:22:02 +0100
>
> > Version 29.2 of Emacs, the extensible text editor, should now
> > be available from your nearest GNU mirror:
>
> Does this mean, the emacs-29 branch is reopen for further commits?
It was never closed. But since this is still a release branch, only
bug-fix changes should be installed that are either very safe or fix
very urgent serious problems.
> Are there plans for an Emacs 29.3?
Not yet. I think we should only consider 29.3 if significant problems
are reported in 29.2 that require quick remediation.
> I'd like to sync recent Tramp changes (available already via GNU ELPA)
> into that branch.
Are they safe enough and/or fix serious problems?
next prev parent reply other threads:[~2024-01-20 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:06 Emacs 29.2 released Eli Zaretskii
2024-01-18 12:06 ` Po Lu
2024-01-18 12:27 ` Eli Zaretskii
2024-01-18 12:38 ` Po Lu
2024-01-18 13:00 ` Eli Zaretskii
2024-01-20 14:41 ` Eli Zaretskii
2024-01-22 6:20 ` Po Lu
2024-01-23 17:41 ` Eli Zaretskii
2024-01-19 1:40 ` pdumper.c Wstringop-overflow warnings with CFLAGS="-O3" [Re: Emacs 29.2 released] N. Jackson
2024-01-19 7:23 ` Eli Zaretskii
2024-01-19 21:22 ` Emacs 29.2 released Michael Albinus
2024-01-20 6:51 ` Eli Zaretskii [this message]
2024-01-20 8:17 ` Michael Albinus
2024-01-20 9:01 ` 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=83cytwv6ox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.