From: Patrick Palka <patrick@parcs.ath.cx>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Updating Readline
Date: Tue, 16 Feb 2016 17:24:00 -0000 [thread overview]
Message-ID: <CA+C-WL-wcTSstsvd3nut73KdZTvDeBi-wRAhgnqbWD+dQEQCRQ@mail.gmail.com> (raw)
In-Reply-To: <83egccwqti.fsf@gnu.org>
On Tue, Feb 16, 2016 at 11:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> This attempt to update Readline in GDB:
>
> https://sourceware.org/ml/gdb-patches/2015-07/msg00422.html
>
> ended up not doing it. We are still at Readline 6.2, AFAICT.
>
> Is there any hope of updating to a newer Readline? Please?
Updating to readline 7.0 (alpha) causes a lot of testsuite regressions
on a number of (non-x86) platforms. It may be safer to first upgrade
to readline 6.3 but in that case there are some local patches that
have to be preserved. So it raises the question of how the ChangeLog
should reflect that some local patches are preserved across the
upgrade, while other local patches are dropped since they've been
applied upstream. The idea is to make it easy to tell which local
patches are currently applied against our upstream copy of readline
especially across upgrades.
next prev parent reply other threads:[~2016-02-16 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 16:41 Eli Zaretskii
2016-02-16 17:24 ` Patrick Palka [this message]
2016-02-16 18:06 ` 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-WL-wcTSstsvd3nut73KdZTvDeBi-wRAhgnqbWD+dQEQCRQ@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