From: Tom Tromey <tom@tromey.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org, Andrew Burgess <aburgess@redhat.com>,
Tom Tromey <tom@tromey.com>,
Richard Bunt <Richard.Bunt@arm.com>
Subject: Re: [PATCH v4 0/6] gdb: introduce limited array lengths while printing values
Date: Fri, 10 Feb 2023 14:17:24 -0700 [thread overview]
Message-ID: <87pmahw78b.fsf@tromey.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2302092205020.7841@tpp.orcam.me.uk> (Maciej W. Rozycki's message of "Fri, 10 Feb 2023 14:18:54 +0000 (GMT)")
>>>>> "Maciej" == Maciej W Rozycki <macro@embecosm.com> writes:
Maciej> I have regression-tested it natively with a `x86_64-linux-gnu' system.
Maciej> OK to apply?
Thank you for doing this. I think this is ok.
Tom
next prev parent reply other threads:[~2023-02-10 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 14:18 Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 1/6] GDB: Switch to using C++ standard integer type limits Maciej W. Rozycki
2023-02-10 21:13 ` Tom Tromey
2023-02-10 14:19 ` [PATCH v4 2/6] GDB: Ignore `max-value-size' setting with value history accesses Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 3/6] GDB: Fix the mess with value byte/bit range types Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 4/6] GDB: Only make data actually retrieved into value history available Maciej W. Rozycki
2023-02-10 21:16 ` Tom Tromey
2023-02-10 14:19 ` [PATCH v4 5/6] GDB/testsuite: Add `-nonl' option to `gdb_test' Maciej W. Rozycki
2023-02-10 14:19 ` [PATCH v4 6/6] GDB: Introduce limited array lengths while printing values Maciej W. Rozycki
2023-02-13 14:45 ` Simon Marchi
2023-02-14 19:20 ` Maciej W. Rozycki
2023-02-23 21:16 ` Maciej W. Rozycki
2023-02-10 21:17 ` Tom Tromey [this message]
2023-02-10 23:50 ` [PATCH v4 0/6] gdb: introduce " Maciej W. Rozycki
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=87pmahw78b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Richard.Bunt@arm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@embecosm.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).