public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: GDB 10 branching - 2020-06-27 Update
Date: Fri, 3 Jul 2020 11:12:05 -0400	[thread overview]
Message-ID: <b8940c8c-d47c-5071-a704-b7b8656a36f6@simark.ca> (raw)
In-Reply-To: <20200703151016.GL5340@adacore.com>

On 2020-07-03 11:10 a.m., Joel Brobecker wrote:
>> I stumbled on a bug introduced by the multi-target patch, which I
>> think should be a blocker for the release (not necessarily the
>> branching).  I marked it with target milestone 10.1 in bugzilla:
>>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=26199
> 
> Thanks Simon. Will you be the one actually looking into the problem?
> I would understand if not (for whatever reason); knowing it would then
> allow us to start searching for someone who could look into it.

I notified Pedro about it, he and/or I will look into it.

Simon

  reply	other threads:[~2020-07-03 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27 15:40 Joel Brobecker
2020-07-01 21:11 ` Rainer Orth
2020-07-01 21:21   ` Joel Brobecker
2020-07-02 21:49 ` Simon Marchi
2020-07-03 15:10   ` Joel Brobecker
2020-07-03 15:12     ` Simon Marchi [this message]
2020-07-10 23:07       ` Pedro Alves
2020-07-03  0:35 ` Simon Marchi
2020-07-03  7:30   ` Eli Zaretskii
2020-07-03 15:06   ` Joel Brobecker
2020-07-03 15:15     ` Simon Marchi
2020-07-03  8:15 ` Sebastian Huber
2020-07-03 13:07   ` Andrew Burgess
2020-07-03 15:07     ` 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=b8940c8c-d47c-5071-a704-b7b8656a36f6@simark.ca \
    --to=simark@simark.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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).