From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 b4f47d2: Use @pxref when necessary
Date: Wed, 24 Nov 2021 21:39:52 +0200 [thread overview]
Message-ID: <831r358hrr.fsf@gnu.org> (raw)
> branch: emacs-28
> commit b4f47d2ee2203a9f22bebeb3d09e0fb3fce2f65e
> Author: Robert Pluim <rpluim@gmail.com>
> Commit: Robert Pluim <rpluim@gmail.com>
>
> Use @pxref when necessary
>
> * doc/lispref/customize.texi (Composite Types):
> * doc/lispref/edebug.texi (Specification List):
> * doc/lispref/variables.texi (Local Variables):
> * doc/misc/efaq.texi (Basic keys):
> (Informational files for Emacs):
> * doc/misc/flymake.texi (Locating a master file):
> * doc/misc/gnus.texi (Don't Panic):
> (Oort Gnus):
> * doc/misc/htmlfontify.texi (Non-interactive):
> * doc/misc/mh-e.texi (More About MH-E):
> * doc/misc/pcl-cvs.texi (Entering PCL-CVS):
> * doc/misc/tramp.texi (Remote processes):
> * doc/misc/vhdl-mode.texi (Indentation Calculation):
> (Custom Indentation Functions): Use @pxref when inside parens.
Please don't install cleanups on the release branch. It isn't worth
even the tiniest risk of gratuitously breaking that branch, even if
this is only in the docs.
I reverted the changeset after merging it to master.
next reply other threads:[~2021-11-24 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 19:39 Eli Zaretskii [this message]
2021-11-25 8:20 ` emacs-28 b4f47d2: Use @pxref when necessary Robert Pluim
2021-11-25 8:44 ` Eli Zaretskii
2021-11-25 8:47 ` Robert Pluim
2021-11-25 9:03 ` Eli Zaretskii
2021-11-25 9:19 ` Robert Pluim
2021-11-25 9:52 ` Eli Zaretskii
2021-11-25 10:18 ` Robert Pluim
2021-11-25 10:53 ` Eli Zaretskii
2021-11-25 14:38 ` Robert Pluim
2021-11-25 16:54 ` Eli Zaretskii
2021-11-25 17: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
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=831r358hrr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).