From: Sandra Loosemore <sandra@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Cc: Simon Marchi <simark@simark.ca>, Pedro Alves <palves@redhat.com>,
Tom Tromey <tromey@adacore.com>
Subject: Re: GDB 10 branching - 2020-07-03 Update
Date: Mon, 6 Jul 2020 18:44:14 -0600 [thread overview]
Message-ID: <18e9b270-429b-1a58-418e-9f543cdae4fc@codesourcery.com> (raw)
In-Reply-To: <238ace7f-3ce5-6f28-73d6-d048391a39bc@codesourcery.com>
On 7/6/20 3:18 PM, Sandra Loosemore wrote:
> On 7/3/20 11:57 AM, Joel Brobecker wrote:
>> Hi everyone,
>>
>> Here is a the current status in terms of the GDB 10 release branching.
>> As you can see, we had a significant number of new items added since
>> last time.
>>
>> As always, let us know if you have comments on those, or if there are
>> other issues you think we should be aware of.
>
> I have a couple of testsuite patches that have not been approved yet.
> Any hope of getting these in?
>
> https://sourceware.org/pipermail/gdb-patches/2020-June/169894.html
> https://sourceware.org/pipermail/gdb-patches/2020-June/169865.html
>
> I'm also working on a third one that I will try to post by the end of
> today; it's for bugs in gdb testglue support introduced in commit
> 24ac169ac5a918cd82b7485935f0c40a094c625e relating to remote-host testing
> and polluting the source directory with .o files in random places.
This is the third patch described above:
https://sourceware.org/pipermail/gdb-patches/2020-July/170224.html
That's all I have in my queue at present, but I know my colleague Paul
Carroll is waiting for approval of an almost-trivial documentation patch
which I've reviewed but can't officially approve:
https://sourceware.org/pipermail/gdb-patches/2020-June/169739.html
-Sandra
next prev parent reply other threads:[~2020-07-07 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 17:57 Joel Brobecker
2020-07-03 18:15 ` Rainer Orth
2020-07-06 21:18 ` Sandra Loosemore
2020-07-07 0:44 ` Sandra Loosemore [this message]
2020-07-07 22:54 ` Kevin Buettner
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=18e9b270-429b-1a58-418e-9f543cdae4fc@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simark@simark.ca \
--cc=tromey@adacore.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