From: Tom Tromey <tom@tromey.com>
To: Christian Biesinger via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>,
Christian Biesinger <cbiesinger@google.com>
Subject: Re: [PATCH 0/4] Import readline 8.0 patches
Date: Tue, 30 Jun 2020 15:19:12 -0600 [thread overview]
Message-ID: <87pn9gckvj.fsf@tromey.com> (raw)
In-Reply-To: <CAPTJ0XG6LMc_oegdTncnSNszZYLYjkL_pupOmcm+HEoxVrwgvg@mail.gmail.com> (Christian Biesinger via Gdb-patches's message of "Mon, 15 Jun 2020 13:21:37 -0500")
I'm going to check this series in now.
Christian> But it would probably be good to update readline/README to mention
Christian> that the 4 patches got applied?
I think we can just rely on readline itself to document the patchlevel.
I'm adding the appended patch to this series to make this more obvious.
Tom
commit b1d34c3e25e2918e14994bd13e4e707e710f9e56
Author: Tom Tromey <tom@tromey.com>
Date: Tue Jun 30 15:17:07 2020 -0600
Update readline/README to mention patchlevel
This updates readline/README to mention the current patchlevel, and
the "git am" approach to importing new upstream patches.
readline/ChangeLog
2020-06-30 Tom Tromey <tom@tromey.com>
* README: Update instructions.
diff --git a/readline/ChangeLog b/readline/ChangeLog
index d13b1e80dd1..69ab913d9fa 100644
--- a/readline/ChangeLog
+++ b/readline/ChangeLog
@@ -1,3 +1,7 @@
+2020-06-30 Tom Tromey <tom@tromey.com>
+
+ * README: Update instructions.
+
2019-11-15 Tom Tromey <tromey@adacore.com>
* configure, Makefile.in: Rebuild.
diff --git a/readline/README b/readline/README
index 9500004e789..54e1c72b197 100644
--- a/readline/README
+++ b/readline/README
@@ -12,3 +12,7 @@ carries.
If your import removes the need for a local patch, please remember to
update this file.
+
+Individual upstream readline patches can be directly imported using
+"git am". You can see the current patch level by looking at
+readline/patchlevel.
prev parent reply other threads:[~2020-06-30 21:19 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 ` [PATCH 0/4] Import readline 8.0 patches Christian Biesinger
2020-06-30 21:19 ` 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=87pn9gckvj.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).