From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master b778e71af7 3/5: Preserve <title> in the Emacs manuals, master e0e3f2b672 2/5: Don't bug out in manual-html-fix-index-2 on newer makeinfo versions
Date: Mon, 04 Jul 2022 13:34:32 +0200 [thread overview]
Message-ID: <87v8sdi01j.fsf@gmail.com> (raw)
In-Reply-To: <20220704110847.A6EDEC051CC@vcs2.savannah.gnu.org> (Lars Ingebrigtsen's message of "Mon, 4 Jul 2022 07:08:47 -0400 (EDT), Mon, 4 Jul 2022 07:08:47 -0400 (EDT)")
>>>>> On Mon, 4 Jul 2022 07:08:47 -0400 (EDT), Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> branch: master
Lars> commit b778e71af7ca8c59917334b4bb1b34cdb52faca9
Lars> Author: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Commit: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Preserve <title> in the Emacs manuals
Lars> * admin/admin.el (manual-html-fix-headers): Preserve the <title>
Lars> element (bug#48334).
>>>>> On Mon, 4 Jul 2022 07:08:47 -0400 (EDT), Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> branch: master
Lars> commit e0e3f2b672bc42da52ac9c7596c7560a88684651
Lars> Author: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Commit: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Don't bug out in manual-html-fix-index-2 on newer makeinfo versions
Lars> * admin/admin.el (manual-html-fix-index-2): Don't bug out if the
Lars> makeinfo version doesn't include <ul>.
Should these two go to the release branch?
Robert
--
next parent reply other threads:[~2022-07-04 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165693292619.18176.8044112007451337025@vcs2.savannah.gnu.org>
[not found] ` <20220704110847.A6EDEC051CC@vcs2.savannah.gnu.org>
2022-07-04 11:34 ` Robert Pluim [this message]
2022-07-04 11:49 ` master b778e71af7 3/5: Preserve <title> in the Emacs manuals, master e0e3f2b672 2/5: Don't bug out in manual-html-fix-index-2 on newer makeinfo versions Eli Zaretskii
2022-07-04 12:15 ` Robert Pluim
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=87v8sdi01j.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.