public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Simon Sobisch <simonsobisch@gnu.org>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 13 release branch created! - [PING][PATCH v8] gdb: split array and string limiting options
Date: Sat, 24 Dec 2022 10:37:10 +0400	[thread overview]
Message-ID: <Y6aeFoz4r00neAzp@adacore.com> (raw)
In-Reply-To: <5ba2419c-3c4c-5c73-4ddc-589d13211ac3@gnu.org>

> Does this mean that the "split array and string limiting options" is now
> unlikely to even land in GDB 13?

This is not excluded, but for it to be in GDB 13, it first needs
to land in master. Once in master, a Global Maintainer can evaluate
its impact on GDB 13 and help determine whether it would be suitable
for GDB 13 or not. My personal opinion looking at the patch series
and its objective is that it would be prudent from a UI perspective
to give this patch some time to mature in master first, before being
introduced in a release.

> After the latest "ping" there was nothing open, maybe I've just missed its
> integration?
> 
> Looking at https://sourceware.org/git/?p=binutils-gdb.git&a=search&h=HEAD&st=commit&s=string
> it doesn't look like the patches are applied yet - but so far I've not seen
> a single reason that those aren't.

The GDB community unfortunately relies on a small group of volunteer
maintainers who dedicate as much time as they can, but we know
unfortunately that this is not enough. This kind of situation is
sadly an unwanted byproduct of the lack of volunteer time.

-- 
Joel

      reply	other threads:[~2022-12-24  6:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221218043825.7A9B080B46@takamaka.gnat.com>
2022-12-18 14:15 ` Simon Sobisch
2022-12-24  6:37   ` Joel Brobecker [this message]

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=Y6aeFoz4r00neAzp@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simonsobisch@gnu.org \
    /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).