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

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

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.

Thanks for making this clear,
Simon

Am 18.12.2022 um 05:38 schrieb Joel Brobecker via Gdb-announce:
> Hello,
> 
> A quick message to announce that the GDB 13 branch has just been created.
> 
> The prerelease snapshots will be available at:
> 
>      ftp://sourceware.org/pub/gdb/snapshots/branch/gdb.tar.xz
> 
> The sources are also accessible via GIT:
> 
>      git clone --single-branch --branch=gdb-13-branch git://sourceware.org/git/binutils-gdb.git
> 
> This announcement has also been posted on the GDB web site at:
> 
>      http://www.sourceware.org/gdb/
> 
> 

       reply	other threads:[~2022-12-18 14:15 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 [this message]
2022-12-24  6:37   ` Joel Brobecker

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=5ba2419c-3c4c-5c73-4ddc-589d13211ac3@gnu.org \
    --to=simonsobisch@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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).