public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>,
	 Simon Marchi <simon.marchi@polymtl.ca>,
	Tom Tromey <tom@tromey.com>,  Simon Sobisch <simonsobisch@web.de>
Subject: [PATCH v7 0/4] gdb: split array and string limiting options
Date: Sat, 29 Oct 2022 14:53:07 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2210281610380.19931@tpp.orcam.me.uk> (raw)

Hi,

 Here is v7 of the series to split array and string limiting options.

 This comprises changes 5/8, 6/8, 7/8 from v6 and 8/8 from v6.1 virtually 
unchanged, rebased against the current master.

 I have regression-tested the changes, with a native `x86_64-linux-gnu' 
configuration.

 See individual change descriptions for details, including updates made to 
change descriptions.

 OK to apply?

  Maciej

             reply	other threads:[~2022-10-29 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 13:53 Maciej W. Rozycki [this message]
2022-10-29 13:53 ` [PATCH v7 1/4] GDB/Python: Use None for `var_zuinteger_unlimited' value set to `unlimited' Maciej W. Rozycki
2022-10-29 15:06   ` Eli Zaretskii
2022-10-29 13:53 ` [PATCH v7 2/4] GDB: Allow arbitrary keywords in integer set commands Maciej W. Rozycki
2022-10-29 15:07   ` Eli Zaretskii
2022-10-31 18:48   ` Simon Marchi
2022-10-31 19:22     ` Simon Marchi
2022-11-24 11:38       ` Maciej W. Rozycki
2022-10-29 13:53 ` [PATCH v7 3/4] GDB: Add a character string limiting option Maciej W. Rozycki
2022-10-29 15:11   ` Eli Zaretskii
2022-10-29 13:53 ` [PATCH v7 4/4] GDB/testsuite: Expand for character string limiting options 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=alpine.DEB.2.20.2210281610380.19931@tpp.orcam.me.uk \
    --to=macro@embecosm.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=simonsobisch@web.de \
    --cc=tom@tromey.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).