public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Cc: Andrew Pinski <apinski@marvell.com>
Subject: Re: [PATCH 1/2] gdb/doc: MPFR is now a necessary requirement
Date: Wed, 29 Mar 2023 13:21:00 -0400	[thread overview]
Message-ID: <102abb23-a0cd-a5ed-11a0-6f2b3ff4314b@gmail.com> (raw)
In-Reply-To: <3d16dc5d-d034-8589-785e-9d994c4f77a5@simark.ca>

Hi Simon,

Le 2023-03-27 à 17:13, Simon Marchi a écrit :
> On 3/10/23 12:46, Philippe Blain via Gdb-patches wrote:
>> Since 99118062785 (Use toplevel configure for GMP and MPFR for gdb,
>> 2022-11-08), MPFR is mandatory for building GDB. That commit adjusted
>> the "Requirements for Building GDB" section of the documentation so that
>> the MPFR entry mentions "now uses" instead of "can use", but left the
>> whole entry under the "Tools/Packages Optional for Building GDB"
>> heading.
>>
>> Move the MPFR entry to the "Tools/Packages Necessary for Building GDB"
>> heading.
>> ---
>>  gdb/doc/gdb.texinfo | 30 +++++++++++++++---------------
>>  1 file changed, 15 insertions(+), 15 deletions(-)
>>
>> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
>> index 2a2077c29d1..218c2da9c86 100644
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -39781,6 +39781,21 @@ you can use the @option{--with-gmp} option or options
>>  @option{--with-gmp-include} and @option{--with-gmp-lib} to specify
>>  its location.
>>  
>> +@item MPFR
>> +@anchor{MPFR}
>> +@value{GDBN} now uses the GNU MPFR multiple-precision floating-point
> 
> Unlike in the NEWS file, where we describe the changes from one version
> to another, the documentation is meant to describe the GDB version is
> comes with.  Therefore, I find it odd to use "now" in the documentation.
> I would just say "GDB uses the GNU MPFR...".  I know it's pre-existing
> text and it's the same in the GMP paragraph, but it sounds weird there
> too.  Imagine reading the doc 20 years down the road, and it says "GDB
> now uses the GNU GMP...", as if it's a new thing.

Yes, I agree. I avoided changing that to keep the existing text as is, and
indeed also because the GMP entry uses the same wording. 

I'll tweak both in v2. 

Thanks,

Philippe.

  reply	other threads:[~2023-03-29 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 17:46 [PATCH 0/2] doc: " 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 [this message]
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=102abb23-a0cd-a5ed-11a0-6f2b3ff4314b@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=apinski@marvell.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).