From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Christian Biesinger via gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [readline] Fix compilation on MinGW
Date: Sun, 15 Sep 2019 01:49:00 -0000 [thread overview]
Message-ID: <CAPTJ0XFSYB2YEsXPV3wcHFNf51V+ZUCtqY6are5QCk3ka9-48A@mail.gmail.com> (raw)
In-Reply-To: <CAPTJ0XEyaVR9wt9pZrKT_au9R3uLbFNhJbAHD_8fmLm7_AQbmg@mail.gmail.com>
On Tue, Aug 13, 2019 at 3:58 PM Christian Biesinger
<cbiesinger@google.com> wrote:
>
> On Tue, Aug 13, 2019 at 2:46 PM Tom Tromey <tom@tromey.com> wrote:
> > It's important to be sure to follow up with upstream readline; and to
> > update the patch in the local tree if Chet uses a different patch.
>
> Will do.
It looks like Chet committed the same patch:
http://git.savannah.gnu.org/cgit/readline.git/diff/colors.c?h=devel&id=c612c3607b183ae654d6c920c729de5444fdb899
Christian
prev parent reply other threads:[~2019-09-15 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 19:04 Christian Biesinger via gdb-patches
2019-08-13 19:46 ` Tom Tromey
2019-08-13 19:59 ` Christian Biesinger via gdb-patches
2019-09-15 1:49 ` Christian Biesinger via gdb-patches [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=CAPTJ0XFSYB2YEsXPV3wcHFNf51V+ZUCtqY6are5QCk3ka9-48A@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--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