From: Eli Zaretskii <eliz@gnu.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: GDB 9.0.90 available for testing
Date: Thu, 19 Dec 2019 19:38:00 -0000 [thread overview]
Message-ID: <83h81w14z1.fsf@gnu.org> (raw)
In-Reply-To: <CAPTJ0XEXfnVDwbppjySQZ766ivW2BiNVa3Jc-as7-1A751OOig@mail.gmail.com> (message from Christian Biesinger on Thu, 19 Dec 2019 13:17:18 -0600)
> From: Christian Biesinger <cbiesinger@google.com>
> Date: Thu, 19 Dec 2019 13:17:18 -0600
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches <gdb-patches@sourceware.org>
>
> > I've now reported the problem to Readline developers. Should I go
> > ahead and patch our local copy, or should I wait for the Readline
> > developers to respond?
>
> Looks like Chet acknowledged the patch:
> https://lists.gnu.org/archive/html/bug-readline/2019-12/msg00003.html
Yes.
> Given the unusual way the readline git repository is managed, probably
> best to patch it locally for now? (not like I have any authority
> here...)
Joel, could you please advise?
next prev parent reply other threads:[~2019-12-19 19:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 21:47 Joel Brobecker
2019-12-11 21:56 ` Joel Brobecker
2019-12-16 17:23 ` Eli Zaretskii
2019-12-16 17:38 ` Simon Marchi
2019-12-16 17:50 ` Eli Zaretskii
2019-12-23 7:54 ` Joel Brobecker
2019-12-16 18:52 ` Christian Biesinger via gdb-patches
2019-12-16 19:18 ` Eli Zaretskii
2019-12-16 19:36 ` Pedro Alves
2019-12-16 19:57 ` Eli Zaretskii
2019-12-16 20:37 ` Christian Biesinger via gdb-patches
2019-12-16 20:38 ` Pedro Alves
2019-12-17 17:25 ` Eli Zaretskii
2019-12-18 20:19 ` Christian Biesinger via gdb-patches
2019-12-19 15:00 ` Eli Zaretskii
2019-12-19 19:17 ` Christian Biesinger via gdb-patches
2019-12-19 19:38 ` Eli Zaretskii [this message]
2019-12-23 7:43 ` Joel Brobecker
2019-12-23 17:32 ` Eli Zaretskii
2019-12-24 3:53 ` Joel Brobecker
2019-12-24 15:30 ` Eli Zaretskii
2020-01-17 20:56 ` Christian Biesinger via gdb-patches
2020-01-17 21:09 ` Eli Zaretskii
2019-12-23 8:01 ` Joel Brobecker
2019-12-23 13:56 ` Eli Zaretskii
2019-12-24 3:49 ` Joel Brobecker
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=83h81w14z1.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