public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@google.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] Import readline 8.0 patches
Date: Mon, 15 Jun 2020 13:21:37 -0500	[thread overview]
Message-ID: <CAPTJ0XG6LMc_oegdTncnSNszZYLYjkL_pupOmcm+HEoxVrwgvg@mail.gmail.com> (raw)
In-Reply-To: <20200614201623.11743-1-tom@tromey.com>

On Sun, Jun 14, 2020 at 3:16 PM Tom Tromey <tom@tromey.com> wrote:
> This series imports the readline 8.0 patches from upstream readline.
>
> I tested these on the x86-64 buildbot builder.
> Let me know what you think.

This is great, I've been meaning to do this but didn't get around to it.

But it would probably be good to update readline/README to mention
that the 4 patches got applied?

Christian

  parent reply	other threads:[~2020-06-15 18:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 20:16 Tom Tromey
2020-06-14 20:16 ` [PATCH 1/4] Readline-8.0 patch 1: fix file descriptor leak with zero-length history file Tom Tromey
2020-06-14 20:16 ` [PATCH 2/4] fix problems moving back beyond start of history Tom Tromey
2020-06-14 20:16 ` [PATCH 3/4] reading history entries with timestamps can result in joined entries Tom Tromey
2020-06-14 20:16 ` [PATCH 4/4] problems restoring the history file are not signaled correctly to the calling application Tom Tromey
2020-06-15 18:21 ` Christian Biesinger [this message]
2020-06-30 21:19   ` [PATCH 0/4] Import readline 8.0 patches Tom Tromey

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=CAPTJ0XG6LMc_oegdTncnSNszZYLYjkL_pupOmcm+HEoxVrwgvg@mail.gmail.com \
    --to=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).