From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, johnw@gnu.org
Subject: Re: Release branch emacs-29
Date: Wed, 30 Nov 2022 07:26:12 -0800 [thread overview]
Message-ID: <CADwFkm=_RHw1Bk2a+x6DEEFw==9qRJ8qTUZqSayNJ4GQ56Gj3w@mail.gmail.com> (raw)
In-Reply-To: <83pmd5ledu.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> What is the status of the manual? I don't see any FIXMEs or notes what else
> should be done -- is it finished?
No, I'm still working on it. This is my main focus currently, and I
expect that the new manual will take at least another week to finish at
the current rate..
Most of the things that needed transferring from README.md are already
done. But there hasn't been much progress since my last update, as I've
focused on the merge in the last week or so.
> Also, I see no announcement on NEWS for use-package -- did I miss it?
There was none indeed, but on the new branch feature/use-package
(replacing scratch/use-package), you can now find it announced in NEWS.
>> Is it preferred that I merge to master or emacs-29 at this point?
>
> To emacs-29, please.
OK, thanks.
> But it looks like you forked the branch from master,
This is fixed on feature/use-package.
next prev parent reply other threads:[~2022-11-30 15:26 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
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 [this message]
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
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='CADwFkm=_RHw1Bk2a+x6DEEFw==9qRJ8qTUZqSayNJ4GQ56Gj3w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@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).