Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"palves@redhat.com" <palves@redhat.com>,
	Nick Alcock <nick.alcock@oracle.com>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: GDB 9.1 release -- 2020-01-17 update
Date: Sat, 18 Jan 2020 07:58:00 -0000	[thread overview]
Message-ID: <1Y_F15YciTHyLIwUopNiHpa7N5QlCXo--MYJx7kxXnfDHdU4LI16W-ervzpyHVis8LUdap-R0Ym0gamWZaU1KAZhlKDCaYzEQMaPTZXGdEs=@gdcproject.org> (raw)
In-Reply-To: <20200117185708.GJ4164@adacore.com>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, January 17, 2020 7:57 PM, Joel Brobecker <brobecker@adacore.com> wrote:

> Hi everyone,
>
> I am hoping that we'll soon be able to push this one out the door!
> We're getting closer, with one last minute addition that I think
> we should indeed evaluate:
>
> -   [IanB/PedroA] output out of order / issue with filtered/unfiltered output order
>     https://sourceware.org/ml/gdb-patches/2019-11/msg00859.html
>
>     Affects cgdb via annotations:
>     https://sourceware.org/bugzilla/show_bug.cgi?id=25190
>
>     Not sure if blocking or not, since there seems to be a workaround;
>     or perhaps the workaround is OK for the annotations, but doesn't
>     work so well for other situations?
>

Hi,

I haven't forgotten this, just had the entire December off whilst on travels.


I retract the 3rd patch in the follow up series, but the first two still are there for review.

https://sourceware.org/ml/gdb-patches/2019-11/msg01120.html
https://sourceware.org/ml/gdb-patches/2019-11/msg01121.html

Regards
Iain


  reply	other threads:[~2020-01-17 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 19:16 Joel Brobecker
2020-01-18  7:58 ` Iain Buclaw [this message]
2020-01-20 12:03 ` Nick Alcock

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='1Y_F15YciTHyLIwUopNiHpa7N5QlCXo--MYJx7kxXnfDHdU4LI16W-ervzpyHVis8LUdap-R0Ym0gamWZaU1KAZhlKDCaYzEQMaPTZXGdEs=@gdcproject.org' \
    --to=ibuclaw@gdcproject.org \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nick.alcock@oracle.com \
    --cc=palves@redhat.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