From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org, michael.albinus@gmx.de
Subject: Re: master 45f6cfb89e2: Merge remote-tracking branch 'origin/scratch/emacs-editorconfig'
Date: Fri, 21 Jun 2024 18:53:49 +0300 [thread overview]
Message-ID: <8634p6l2b6.fsf@gnu.org> (raw)
In-Reply-To: <87sex6baux.fsf@gmail.com> (message from Robert Pluim on Fri, 21 Jun 2024 16:59:18 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org, Michael Albinus <michael.albinus@gmx.de>
> Date: Fri, 21 Jun 2024 16:59:18 +0200
>
> >>>>> On Fri, 21 Jun 2024 16:54:46 +0200, Robert Pluim <rpluim@gmail.com> said:
>
> Robert> (Iʼm using texinfo 6.8)
>
> Robert> Iʼd expect to see an entry in an @menu somewhere for the node. If you
> Robert> tell use where you think it should go, I can add it.
>
> Actually, the resulting info file has an automatically generated menu
> at the end of "Per-Directory Local Variables" pointing at the new
> node, so maybe itʼs a warning thatʼs been fixed in a later version.
>
> I guess we could add a menu there to get rid of the warning.
Please just fix all the problems. There's no need to discuss such
trivia.
next prev parent reply other threads:[~2024-06-21 15:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171897896087.14973.179765515924525117@vcs2.savannah.gnu.org>
[not found] ` <20240621140923.49EF2C1FB70@vcs2.savannah.gnu.org>
2024-06-21 14:24 ` master 45f6cfb89e2: Merge remote-tracking branch 'origin/scratch/emacs-editorconfig' Michael Albinus
2024-06-21 14:30 ` Robert Pluim
2024-06-21 14:41 ` Stefan Monnier
2024-06-21 14:54 ` Robert Pluim
2024-06-21 14:59 ` Robert Pluim
2024-06-21 15:53 ` Eli Zaretskii [this message]
2024-06-21 15:56 ` Eli Zaretskii
2024-06-21 19:56 ` Stefan Monnier
2024-06-22 6:15 ` Eli Zaretskii
2024-06-21 15:54 ` 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=8634p6l2b6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
/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.