From: Patrick Palka <patrick@parcs.ath.cx>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Readline patches
Date: Tue, 14 Jul 2015 20:51:00 -0000 [thread overview]
Message-ID: <CA+C-WL8menxQJyMYtm3kjfCL_utsVEtTefSmsdoDJcXNrbu_BA@mail.gmail.com> (raw)
In-Reply-To: <83r3oa7bms.fsf@gnu.org>
On Tue, Jul 14, 2015 at 4:00 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> Please see
>
> http://lists.gnu.org/archive/html/bug-readline/2015-07/msg00010.html
> http://lists.gnu.org/archive/html/bug-readline/2015-07/msg00011.html
>
> The Readline maintainer says the patches I sent back in January are
> all in the latest Readline sources, and yet they are not in the GDB
> Git repository, although AFAIR our Readline was resync'ed lately.
A series was posted (by me) to update our sources to version 6.3 but
was never committed.
>
> What should be done to have the latest Readline sources in GDB?
Since readline 7.0 alpha is out, I think we might as well sync
straight to it now that GDB 7.10 is branched. And we can quickly sync
subsequent alpha/beta releases of readline 7.0 as they get released. A
big advantage of syncing straight to readline 7.0 is that this is the
first version contains all of GDB's currently local patches to
readline so we won't have to worry about reapplying any local patches.
I'll try to get a patchset ready for tomorrow, assuming readline 7.10
does not cause any major regressions from 6.3.
next prev parent reply other threads:[~2015-07-14 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 20:00 Eli Zaretskii
2015-07-14 20:51 ` Patrick Palka [this message]
2015-07-15 2:41 ` Eli Zaretskii
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=CA+C-WL8menxQJyMYtm3kjfCL_utsVEtTefSmsdoDJcXNrbu_BA@mail.gmail.com \
--to=patrick@parcs.ath.cx \
--cc=eliz@gnu.org \
--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