Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
	 gdb-patches@sourceware.org,
	 Patrick Palka <patrick@parcs.ath.cx>
Subject: Re: Upgrading readline
Date: Thu, 18 Oct 2018 22:11:00 -0000	[thread overview]
Message-ID: <87va5yaoso.fsf@tromey.com> (raw)
In-Reply-To: <040744ad-dd95-8be2-c3b5-bae6a9034a91@redhat.com> (Pedro Alves's	message of "Sat, 29 Sep 2018 19:19:56 +0100")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> On 09/29/2018 12:52 PM, Tom Tromey wrote:
>> I took a look at what it would take to upgrade to the latest readline 7
>> patch release.  I have a few questions, mostly about Windows-related
>> preprocessor defines.

Pedro> Thanks for doing this.  Note that Patrick Palka attempted this
Pedro> a couple of years back.  The update went into master, but
Pedro> was subsequently reverted because of problems on non-x86 ports.

Pedro> See:
Pedro>  https://sourceware.org/ml/gdb-patches/2015-07/msg00422.html
Pedro>  https://sourceware.org/ml/gdb-patches/2015-07/msg00759.html

Pedro> And:
Pedro>  https://sourceware.org/ml/gdb-patches/2016-02/msg00484.html

Yeah, I saw those - he was trying with 7.0 alpha, and I was hoping maybe
doing it with a later (non-alpha) version would help.

I have a patch.  And, I went through the local changes and I think none
of them are needed, so I've removed them one-by-one in the resulting
series.

However, it's too big to push through "buildbot try".
So, it may be quite some time until I'm able to test it suitably.
If someone wants to help with this, it's in my github repository.

Tom


      reply	other threads:[~2018-10-18 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 11:53 Tom Tromey
2018-09-29 13:53 ` Eli Zaretskii
2018-09-30 20:31   ` Tom Tromey
2018-09-29 18:20 ` Pedro Alves
2018-10-18 22:11   ` Tom Tromey [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=87va5yaoso.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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