From: Bastien <bzg@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Release branch emacs-29
Date: Tue, 29 Nov 2022 08:08:06 +0100 [thread overview]
Message-ID: <87sfi2jl0p.fsf@gnu.org> (raw)
In-Reply-To: <83wn7flz9f.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 28 Nov 2022 20:17:32 +0200")
Hi Eli,
Eli Zaretskii <eliz@gnu.org> writes:
> From now on please install bug fixes to the emacs-29 branch (they will be
> merged to master soon enough), while new features and improvements in
> existing features should be installed on master.
Org 9.6 has just been released:
https://list.orgmode.org/87pmd6p7qs.fsf@gnu.org/T/#u
I interpreted "late november" a bit too extremely and thought tomorrow
was the deadline for merging Org 9.6 with the Emacs development branch.
Is it okay to make an exception and sync 9.6 with the emacs-29 branch?
Thanks,
--
Bastien
next prev parent reply other threads:[~2022-11-29 7:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 18:17 Release branch emacs-29 Eli Zaretskii
2022-11-28 19:04 ` Eli Zaretskii
2022-11-29 7:08 ` Bastien [this message]
2022-11-29 13:07 ` Eli Zaretskii
2022-11-30 3:46 ` Bastien
2022-11-29 13:26 ` Akib Azmain Turja
2022-11-30 12:32 ` Stefan Monnier
2022-11-30 20:37 ` Akib Azmain Turja
2022-11-30 13:39 ` Eli Zaretskii
2022-11-30 20:44 ` Akib Azmain Turja
2022-12-01 6:05 ` Eli Zaretskii
2022-11-30 16:47 ` Stefan Monnier
2022-11-30 20:36 ` Akib Azmain Turja
2022-12-01 6:03 ` Eli Zaretskii
2022-12-01 16:47 ` Akib Azmain Turja
2022-12-01 18:19 ` Eli Zaretskii
2022-11-29 19:24 ` Stefan Kangas
2022-11-29 20:00 ` Eli Zaretskii
2022-11-30 15:26 ` Stefan Kangas
2022-12-08 0:20 ` Stefan Kangas
2022-12-08 8:37 ` Eli Zaretskii
2022-12-08 22:20 ` Stefan Kangas
2022-12-09 6:52 ` Eli Zaretskii
2022-12-09 14:35 ` 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=87sfi2jl0p.fsf@gnu.org \
--to=bzg@gnu.org \
--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 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.