From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
ibuclaw@gdcproject.org, nick.alcock@oracle.com
Subject: Re: Propose we release GDB 9.1 next weekend (Feb 01-02)
Date: Sun, 26 Jan 2020 16:07:00 -0000 [thread overview]
Message-ID: <83a76ap5p6.fsf@gnu.org> (raw)
In-Reply-To: <20200126114033.GA20733@adacore.com> (message from Joel Brobecker on Sun, 26 Jan 2020 15:40:33 +0400)
> Date: Sun, 26 Jan 2020 15:40:33 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: palves@redhat.com, Iain Buclaw <ibuclaw@gdcproject.org>, Nick Alcock <nick.alcock@oracle.com>, Eli Zaretskii <eliz@gnu.org>
>
> - [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.
>
> => Still waiting for Nick. Rather than putting more pressure
> on Nick, I propose we go with Eli's patch of providing
> fallback errno values. When Nick is able to confirm
> his final patch, we'll decide whether to backport or
> stay with the simpler patch from Eli.
Fine with me (obviously).
Thanks.
next prev parent reply other threads:[~2020-01-26 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 15:41 Joel Brobecker
2020-01-26 16:07 ` Eli Zaretskii [this message]
2020-01-28 16:43 ` Nick Alcock
2020-01-28 17:06 ` Hannes Domani via gdb-patches
[not found] ` <ee83b6c0-8e18-eb1e-18c8-f9df79b547d7@simark.ca>
2020-01-28 17:37 ` Hannes Domani via gdb-patches
2020-02-01 3:20 ` Jonah Graham
2020-02-01 8:00 ` Simon Marchi
2020-02-01 12:17 ` Joel Brobecker
2020-02-01 12:58 ` Jonah Graham
2020-02-01 13:06 ` Joel Brobecker
2020-02-05 10:08 ` Tom Tromey
2020-02-01 15:45 ` Simon Marchi
2020-02-01 15:37 ` Simon Marchi
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=83a76ap5p6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.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