public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Propose GDB 10 branch this Fri-Sun (Sep 11-13) [2020-09-05 Update]
Date: Tue, 8 Sep 2020 10:06:34 -0700	[thread overview]
Message-ID: <20200908170634.GD18641@adacore.com> (raw)
In-Reply-To: <CAPTJ0XEo9re56DpRausp7xzGtPA5NwFUihSorPjCDt-w6rYOGw@mail.gmail.com>

> > Below is another status update before branching. We're almost there,
> > and if all goes well, I propose we create the branch during the weekend
> > of Fri-Sun Sep 11-13, immediately followed by creating the first
> > prerelease.
> 
> This bug was just filed with patch:
> https://sourceware.org/bugzilla/show_bug.cgi?id=26586
> 
> It seems like that patch would be good to have for gdb 10, though it
> probably doesn't have to block branching.

Thanks for the heads up Cristian. I marked it 10.1 for the target
milestone to remember about it. I agree it's not branch blocking.
It shouldn't be release blocking either because, as far as I can tell,
the problem was also in GDB 8.2 and GDB 9, but given the type of fix
we are talking about, perhaps worth waiting a bit for...

-- 
Joel

  reply	other threads:[~2020-09-08 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 20:53 Joel Brobecker
2020-09-07  0:07 ` Kamil Rytarowski
2020-09-07 20:02   ` Simon Marchi
2020-09-08 13:49     ` Joel Brobecker
2020-09-08 13:51       ` Kamil Rytarowski
2020-09-10 15:01         ` Simon Marchi
2020-09-08 15:40 ` Christian Biesinger
2020-09-08 17:06   ` Joel Brobecker [this message]
2020-09-10 15:03 ` Simon Marchi

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=20200908170634.GD18641@adacore.com \
    --to=brobecker@adacore.com \
    --cc=cbiesinger@google.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).