From: Philippe Blain <levraiphilippeblain@gmail.com>
To: gdb-patches@sourceware.org
Cc: Andrew Pinski <apinski@marvell.com>
Subject: [PATCH 0/2] doc: MPFR is now a necessary requirement
Date: Fri, 10 Mar 2023 12:46:55 -0500 [thread overview]
Message-ID: <20230306-doc-require-mpfr-fix-v1-0-8f207504dd3e@gmail.com> (raw)
This short series moves the "MPFR" requirement in the doc under the
"Tools/Packages Necessary for Building GDB" heading and uniformizes the wording
between the GMP and MPFR entries.
I tested the HTML doc build.
---
Philippe Blain (2):
gdb/doc: MPFR is now a necessary requirement
gdb/doc: uniformize wording for GMP and MPFR entries
gdb/doc/gdb.texinfo | 31 +++++++++++++++----------------
1 file changed, 15 insertions(+), 16 deletions(-)
---
base-commit: 4c9066e322f46faf9d753be6ff3e6a09ae668f86
change-id: 20230306-doc-require-mpfr-fix-65e7105fc410
--
b4
next reply other threads:[~2023-03-10 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:46 Philippe Blain [this message]
2023-03-10 17:46 ` [PATCH 1/2] gdb/doc: " Philippe Blain
2023-03-10 19:15 ` Eli Zaretskii
2023-03-27 21:13 ` Simon Marchi
2023-03-29 17:21 ` Philippe Blain
2023-03-10 17:46 ` [PATCH 2/2] gdb/doc: uniformize wording for GMP and MPFR entries Philippe Blain
2023-03-10 19:17 ` Eli Zaretskii
2023-03-13 16:45 ` Philippe Blain
2023-03-14 12:08 ` Eli Zaretskii
2023-03-14 17:12 ` Philippe Blain
2023-03-14 17:38 ` Philippe Blain
2023-03-14 19:41 ` Eli Zaretskii
2023-03-14 19:48 ` Philippe Blain
2023-03-14 19:38 ` Eli Zaretskii
2023-03-27 21:18 ` Simon Marchi
2023-03-25 22:04 ` [PATCH 0/2] doc: MPFR is now a necessary requirement Philippe Blain
[not found] ` <20230306-doc-require-mpfr-fix-v2-0-7de0f692b004@gmail.com>
[not found] ` <837cuqsbfb.fsf@gnu.org>
2023-04-07 13:19 ` [PATCH v2 " Philippe Blain
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=20230306-doc-require-mpfr-fix-v1-0-8f207504dd3e@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=apinski@marvell.com \
--cc=gdb-patches@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).