From: Eli Zaretskii <eliz@gnu.org>
To: palves@redhat.com
Cc: gdb@crelg.com, gdb-patches@sourceware.org
Subject: Re: Enabled TUI mode on MSYS2
Date: Sat, 17 Sep 2016 09:39:00 -0000 [thread overview]
Message-ID: <83h99e50h5.fsf@gnu.org> (raw)
In-Reply-To: <83mvj652ly.fsf@gnu.org> (message from Eli Zaretskii on Sat, 17 Sep 2016 11:53:29 +0300)
> Date: Sat, 17 Sep 2016 11:53:29 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: gdb@crelg.com, gdb-patches@sourceware.org
>
> > Cc: gdb@crelg.com, gdb-patches@sourceware.org
> > From: Pedro Alves <palves@redhat.com>
> > Date: Wed, 14 Sep 2016 20:04:09 +0100
> >
> > > Yes. But if importing a newer Readline is not going to happen soon, I
> > > think we should apply my patches to our copy of Readline, to avoid
> > > these issues.
> >
> > FAOD, as mentioned upthread, that'd be fine with me.
>
> Done.
I get messages about my commit broke the build. But I don't
understand the nature of the breakage: all of the errors complain
about min and max in the 'gdb' directory, whereas I didn't change
anything in that directory, and didn't introduce any calls or
definitions of min or max.
Help will be appreciated.
Sorry for the mess.
next prev parent reply other threads:[~2016-09-17 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 21:21 Giah de Barag
2016-09-14 2:42 ` Eli Zaretskii
2016-09-14 6:32 ` Giah de Barag
2016-09-14 17:22 ` Eli Zaretskii
2016-09-14 17:33 ` Pedro Alves
2016-09-14 18:33 ` Giah de Barag
2016-09-14 18:36 ` Pedro Alves
2016-09-14 18:59 ` Eli Zaretskii
2016-09-14 19:04 ` Pedro Alves
2016-09-17 8:53 ` Eli Zaretskii
2016-09-17 9:39 ` Eli Zaretskii [this message]
2016-09-18 23:40 ` Pedro Alves
2016-09-20 22:45 ` Sergio Durigan Junior
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=83h99e50h5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@crelg.com \
--cc=palves@redhat.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).