From: Tom Tromey <tromey@adacore.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Tom Tromey <tromey@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] Wrap help strings at 80 columns
Date: Fri, 07 Jun 2024 10:50:25 -0600 [thread overview]
Message-ID: <87v82kk88e.fsf@tromey.com> (raw)
In-Reply-To: <DM8PR11MB57499DD813F2FF94566CAE0CDEF92@DM8PR11MB5749.namprd11.prod.outlook.com> (Markus T. Metzger's message of "Wed, 5 Jun 2024 15:11:13 +0000")
>>>>> Metzger, Markus T <markus.t.metzger@intel.com> writes:
>> When READ-WRITE, allow accesses to read-only and read-write memory during \
> Looks like there is one missing.
Thanks for noticing this. This pointed out that the unit test was not
checking the last line of the doc string; and this found a significant
number of new problems...
Tom
next prev parent reply other threads:[~2024-06-07 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:57 [PATCH 0/4] Require help text to fit in " Tom Tromey
2024-06-03 17:57 ` [PATCH 1/4] Call gdbpy_fix_doc_string_indentation for function help Tom Tromey
2024-06-03 17:57 ` [PATCH 2/4] Wrap help strings at 80 columns Tom Tromey
2024-06-05 15:11 ` Metzger, Markus T
2024-06-07 16:50 ` Tom Tromey [this message]
2024-06-03 17:57 ` [PATCH 3/4] Wrap help options when building help string Tom Tromey
2024-06-03 17:57 ` [PATCH 4/4] Ensure that help text fits in 80 columns Tom Tromey
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=87v82kk88e.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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).