Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>, gdb-patches@sourceware.org
Cc: jan.kratochvil@redhat.com
Subject: Re: [PATCH] [RFC] Sync readline to version 6.3 patchlevel 8
Date: Thu, 14 May 2015 09:29:00 -0000	[thread overview]
Message-ID: <55546AEF.9070505@redhat.com> (raw)
In-Reply-To: <1431562331-20448-1-git-send-email-patrick@parcs.ath.cx>

On 05/14/2015 01:12 AM, Patrick Palka wrote:
> This patch syncs our upstream copy of readline to version 6.3
> patchlevel 8.
> 
> I basically copied what was done when Jan updated to readline 6.2 in
> 2011: http://sourceware.org/ml/gdb-patches/2011-05/msg00003.html
> 
> Specifically, I:
> 
> 1. Extracted the readline 6.3 tarball on top of readline/
> 2. Applied patches 1-8 from ftp://ftp.cwru.edu/pub/bash/readline-6.3-patches/
> 3. Omitted all the files in doc/ that were intentionally omitted before.
> 4. Regenerated readline/configure and readline/examples/rlfe/configure
>    using autoconf 2.64.  No other configure files needed regenerating.
> 5. Reapplied the only local patch since the update to readline 6.2 that
>    has not already been applied to readline 6.3, 05942d8a1 ("Fix
>    executable indicator in file name completeion on Windows.").  This
>    particular patch has been applied upstream but readline 6.3 does not
>    have it.  Whether or not a local patch has already been applied to
>    readline 6.3 was determined via manual inspection.  (Wasn't too bad
>    really.)
> 
> The new files to make it into the tree are:
> 
>     colors.{c,h}
>     configure.ac
>     parse-colors.{c,h}
>     examples/hist_erasedups.c
>     examples/hist_purgecmd.c
> 
> Deleted files:
> 
>     configure.in
> 
> I've been using this patch locally for a few months now and I've
> experienced only a single regression which has already been preemptively
> fixed by 8900d71e3 ("Explicitly call rl_resize_terminal() in TUI's
> SIGWINCH handler").  Other than that, no issues in either the CLI or the
> TUI, or changes in the testsuite.  Though I have only been able to test
> this patch on Linux.
> 
> Have I missed anything?  What else should be done in order to sync our
> copy of readline?  Unlike the last sync from 5.1 to 6.2, this sync to
> 6.3 is quite minor and hopefully painless.
> 
> Because the commit is so big and so mechanical I elected to create a
> branch users/ppalka/readline-6.3-update where you can view/test the
> change.

(I haven't looked at the branch,) but it all sounds great to me.

Many thanks for doing all this.

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-05-14  9:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14  0:12 Patrick Palka
2015-05-14  1:40 ` Patrick Palka
2015-05-18 11:38   ` Patrick Palka
2015-05-18 11:41     ` Patrick Palka
2015-06-18 10:41       ` Pedro Alves
2015-05-14  9:29 ` Pedro Alves [this message]
2015-05-16  1:00 ` Doug Evans
2015-05-16 14:59   ` Patrick Palka
2015-05-16 15:23     ` Doug Evans
2015-05-16 15:25       ` Jan Kratochvil
2015-05-16 15:50         ` Patrick Palka
2015-05-16 16:06           ` Jan Kratochvil
2015-05-16 15:51         ` Doug Evans
2015-06-18 10:39           ` Pedro Alves
2015-06-18 13:47             ` Doug Evans
2015-06-18 14:08               ` Pedro Alves
2015-06-18 14:20                 ` Doug Evans

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=55546AEF.9070505@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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