From: Andreas Schwab <schwab@suse.de>
To: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH] tunables.texi: Change \code{1} to @code{1}
Date: Thu, 23 Feb 2023 10:01:38 +0100 [thread overview]
Message-ID: <mvmbklkpxfx.fsf@suse.de> (raw)
In-Reply-To: <xnbkll80xm.fsf@greed.delorie.com> (DJ Delorie via Libc-alpha's message of "Wed, 22 Feb 2023 23:23:33 -0500")
On Feb 22 2023, DJ Delorie via Libc-alpha wrote:
> I'll note that the manual doesn't seem to be built by "make all" - it is
> built for an install, so "make check" builds it for the testroot - ONCE.
> It took me a while to figure out how to reliably test texinfo changes.
You can also use make info.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2023-02-23 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:52 [PATCH v3] x86-64: Add glibc.cpu.prefer_map_32bit_exec [BZ #28656] H.J. Lu
2023-02-22 15:02 ` Carlos O'Donell
2023-02-23 3:43 ` DJ Delorie
2023-02-23 4:08 ` [PATCH] tunables.texi: Change \code{1} to @code{1} H.J. Lu
2023-02-23 4:23 ` DJ Delorie
2023-02-23 9:01 ` Andreas Schwab [this message]
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=mvmbklkpxfx.fsf@suse.de \
--to=schwab@suse.de \
--cc=dj@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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.
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).