From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: GDB 10 branching - 2020-06-27 Update
Date: Sat, 11 Jul 2020 00:07:53 +0100 [thread overview]
Message-ID: <06929a0a-d2e2-7a24-69b4-b0064962eec1@palves.net> (raw)
In-Reply-To: <b8940c8c-d47c-5071-a704-b7b8656a36f6@simark.ca>
On 7/3/20 4:12 PM, Simon Marchi wrote:
> 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.
This one's now fixed.
next prev parent reply other threads:[~2020-07-10 23:07 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
2020-07-10 23:07 ` Pedro Alves [this message]
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=06929a0a-d2e2-7a24-69b4-b0064962eec1@palves.net \
--to=pedro@palves.net \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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).