From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>,
Philippe Blain <levraiphilippeblain@gmail.com>
Cc: gdb-patches@sourceware.org, apinski@marvell.com
Subject: Re: [PATCH 2/2] gdb/doc: uniformize wording for GMP and MPFR entries
Date: Mon, 27 Mar 2023 17:18:34 -0400 [thread overview]
Message-ID: <89f5b249-378b-1b19-1885-f12028b96c78@simark.ca> (raw)
In-Reply-To: <83y1nzsfgu.fsf@gnu.org>
> My preference is to install only the first of these, for the reasons I
> explained, but I'm waiting to hear opinions of others, if they differ.
Since you are waiting for some opinion, I'll give mine. I like the more
uniform text after patch 2. I like having the description of why GDB
uses the library at the start (even if it's just informative, it doesn't
help the user accomplish anything in the end). I think that the change
that mentions the "configure" script is nice, otherwise it can be
unclear where to use those --with-gmp/--with-gmp-include/--with-gmp-lib
options.
Simon
next prev parent reply other threads:[~2023-03-27 21:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:46 [PATCH 0/2] doc: MPFR is now a necessary requirement Philippe Blain
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 [this message]
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=89f5b249-378b-1b19-1885-f12028b96c78@simark.ca \
--to=simark@simark.ca \
--cc=apinski@marvell.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=levraiphilippeblain@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.
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).