From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>,
Bernd Edlinger <bernd.edlinger@hotmail.de>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Enable building GDB without installed libtermcap
Date: Thu, 26 Feb 2015 17:29:00 -0000 [thread overview]
Message-ID: <54EF57E9.70403@redhat.com> (raw)
In-Reply-To: <CADPb22Tyn=4uUXBHh_H=u_XMvShZVjCbC_DgrL0GujxSx=NGog@mail.gmail.com>
On 02/24/2015 08:29 PM, Doug Evans wrote:
> On Tue, Feb 24, 2015 at 11:34 AM, Mike Frysinger <vapier@gentoo.org> wrote:
>> On 24 Feb 2015 19:13, Bernd Edlinger wrote:
>>> Maybe the name windows-termcap.c is a bit misleading,
>>> because my target is mostly some embedded linux.
>>
>> yes, i think you should rename it to "stub-termcap.c" or something similar.
>> -mike
>
> Agreed.
Alright, that much is noncontroversial, I think.
Done:
https://sourceware.org/ml/gdb-patches/2015-02/msg00772.html
--
Pedro Alves
next prev parent reply other threads:[~2015-02-26 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB118-W1951908395674D538A9BBDE4280@phx.gbl>
2015-02-23 16:06 ` Pedro Alves
2015-02-23 16:18 ` Pedro Alves
2015-02-23 19:27 ` Mike Frysinger
2015-02-23 19:44 ` Eli Zaretskii
2015-02-23 20:33 ` Mike Frysinger
2015-02-23 21:00 ` Eli Zaretskii
2015-02-24 18:18 ` Bernd Edlinger
2015-02-24 19:34 ` Mike Frysinger
2015-02-24 20:29 ` Doug Evans
2015-02-26 17:29 ` Pedro Alves [this message]
2015-02-26 17:48 ` Pedro Alves
2015-02-26 18:00 ` Eli Zaretskii
2015-02-26 18:45 ` Pedro Alves
2015-02-26 18:55 ` Eli Zaretskii
2015-02-26 19:14 ` Pedro Alves
2015-04-02 17:34 ` Bernd Edlinger
2015-04-06 11:42 ` Pedro Alves
2015-02-26 19:15 ` Bernd Edlinger
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=54EF57E9.70403@redhat.com \
--to=palves@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=dje@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