From: Nick Alcock <nick.alcock@oracle.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
Iain Buclaw <ibuclaw@gdcproject.org>,
Nick Alcock <nick.alcock@oracle.com>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: GDB 9.1 release -- 2020-01-17 update
Date: Mon, 20 Jan 2020 12:03:00 -0000 [thread overview]
Message-ID: <87pnfexvor.fsf@esperi.org.uk> (raw)
In-Reply-To: <20200117185708.GJ4164@adacore.com> (Joel Brobecker's message of "Fri, 17 Jan 2020 19:57:08 +0100")
On 17 Jan 2020, Joel Brobecker uttered the following:
> Still Open:
>
> - [Eliz/NickA/JoelB] libtcf fails to build on MinGW
> https://sourceware.org/bugzilla/show_bug.cgi?id=25155
>
> The only issue left to fix is the issue with errno.
> Nick Alcock provided a prototype patch, and said he would
> inform us when the final patch is pushed. I privately sent
> a request for info earlier today.
Yeah sorry: delays caused by work deadlines and now a decaying molar
wrecking my ability to concentrate :( all short-term, a few days I hope.
prev parent reply other threads:[~2020-01-20 10:36 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
2020-01-20 12:03 ` Nick Alcock [this message]
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=87pnfexvor.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--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