Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: Updating Readline
Date: Tue, 16 Feb 2016 18:06:00 -0000	[thread overview]
Message-ID: <83bn7gwmw1.fsf@gnu.org> (raw)
In-Reply-To: <CA+C-WL-wcTSstsvd3nut73KdZTvDeBi-wRAhgnqbWD+dQEQCRQ@mail.gmail.com>	(message from Patrick Palka on Tue, 16 Feb 2016 12:23:24 -0500)

> From: Patrick Palka <patrick@parcs.ath.cx>
> Date: Tue, 16 Feb 2016 12:23:24 -0500
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.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.

Yes, I know.  That old thread says that, and it was the reason the
upgrade never happened back then.

> It may be safer to first upgrade to readline 6.3

Does it make sense to upgrade to 6.3 when 7.0 is already in beta?  We
do want eventually start using a newer Readline, I hope.  If so, we
need to start fixing the problems the update causes, otherwise we will
be left behind.  Either our tests need to be amended or Readline 7.0 is
not a simple drop-in replacement, and more of our code needs to be
changed.

But I don't think it makes sense to do nothing, or start using an old
version of Readline.  We will be just deferring the problem for later,
and it won't fix itself, I think.

Thanks.


      reply	other threads:[~2016-02-16 18:06 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
2016-02-16 18:06   ` Eli Zaretskii [this message]

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=83bn7gwmw1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=patrick@parcs.ath.cx \
    /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