From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Start of Emacs 30 release cycle
Date: Mon, 24 Jun 2024 10:32:21 +0200 [thread overview]
Message-ID: <8734p2212i.fsf@gmx.net> (raw)
In-Reply-To: <86frt3eptb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Jun 2024 16:44:48 +0300")
On Sun, 23 Jun 2024 16:44:48 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
> I've created the emacs-30 release branch, which will be used to
> release the Emacs 30.x series. Changes installed on this branch
> should be bugfixes that do not modify too low-level code, and thus
> don't risk destabilizing the codebase we have on that branch now. All
> the other changes, including new features, should be installed on
> master, as usual. If in doubt whether a particular change should be
> installed on master or on the release branch, please ask here.
Can the patches for wid-edit.el in bug#69942 and bug#70594 still be
installed on the emacs-30 branch? In particular, the patch in bug#70594
fixes (or, as I see it, completes) commit 91333dacfa1, which is on the
emacs-30 branch.
Steve Berman
next prev parent reply other threads:[~2024-06-24 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 13:44 Start of Emacs 30 release cycle Eli Zaretskii
2024-06-24 8:32 ` Stephen Berman [this message]
2024-06-24 12:47 ` Eli Zaretskii
2024-06-24 13:49 ` Stephen Berman
2024-06-24 15:05 ` Eli Zaretskii
2024-06-25 10:41 ` Stephen Berman
2024-06-25 13:48 ` Eli Zaretskii
2024-06-26 6:45 ` Stephen Berman
2024-06-25 14:10 ` Robert Pluim
2024-06-25 14:48 ` Stephen Berman
2024-06-25 15:09 ` Robert Pluim
2024-06-25 15:57 ` Eli Zaretskii
2024-06-26 6:53 ` Stephen Berman
2024-06-26 9:27 ` Robert Pluim
2024-07-01 13:15 ` nxml comments fix (was: Start of Emacs 30 release cycle) Konstantin Kharlamov
2024-07-01 13:41 ` Eli Zaretskii
2024-07-01 14:00 ` Konstantin Kharlamov
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 6:48 Start of Emacs 30 release cycle Pedro Andres Aranda Gutierrez
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=8734p2212i.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--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).