From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release 2019-12-23 update
Date: Fri, 27 Dec 2019 07:49:00 -0000 [thread overview]
Message-ID: <83zhfep5r8.fsf@gnu.org> (raw)
In-Reply-To: <CAPTJ0XGyazMtbxwwHCoQmaRBd_c-KaEpj+rLBkkQtF7PJy64Cw@mail.gmail.com> (message from Christian Biesinger on Thu, 26 Dec 2019 23:39:36 +0100)
> From: Christian Biesinger <cbiesinger@google.com>
> Date: Thu, 26 Dec 2019 23:39:36 +0100
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches <gdb-patches@sourceware.org>
>
> > I added an attachment with the patch to the Bugzilla report, it should
> > appear shortly on the bug-binutils mailing list. Let's see what
> > happens next.
>
> I don't know how binutils works, but if they work like gdb, it may be
> worth sending the patch to the binutils mailing list directly instead
> of relying on people to read bug-binutils?
I'm fine with that, but if they don't read bug-binutils, then why does
that list even exist?
I actually suggest that Joel or Pedro post to the binutils mailing
list quoting the Bugzilla report and/or the bug-binutils messages
https://lists.gnu.org/archive/html/bug-binutils/2019-11/msg00006.html
https://lists.gnu.org/archive/html/bug-binutils/2019-12/msg00162.html
and telling the Binutils folks that this currently blocks a GDB
release. I think this would have a much more profound effect than me
doing the same.
Or we could make the release regardless of the libctf issues with
MinGW.
next prev parent reply other threads:[~2019-12-27 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 9:30 Joel Brobecker
2019-12-23 14:14 ` Eli Zaretskii
2019-12-23 14:32 ` Eli Zaretskii
2019-12-24 3:47 ` Joel Brobecker
2019-12-24 12:24 ` Andrew Burgess
2019-12-24 15:52 ` Eli Zaretskii
2020-01-03 16:21 ` Tom Tromey
2019-12-24 16:21 ` Eli Zaretskii
2019-12-26 22:40 ` Christian Biesinger via gdb-patches
2019-12-27 7:49 ` Eli Zaretskii [this message]
2019-12-25 21:36 ` Andrew Burgess
2020-01-02 10:56 ` Joel Brobecker
2020-01-06 22:00 ` Andrew Burgess
2019-12-28 16:22 ` Hannes Domani via gdb-patches
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=83zhfep5r8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
/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).