From: Mark Mitchell <mark@codesourcery.com>
To: Christopher Faylor <me@cgf.cx>
Cc: gdb-patches@sources.redhat.com, chet.ramey@case.edu,
Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: Guidance re. MinGW and readline
Date: Mon, 18 Jul 2005 14:34:00 -0000 [thread overview]
Message-ID: <42DBBDA8.5000602@codesourcery.com> (raw)
In-Reply-To: <20050718135801.GA17333@trixie.casa.cgf.cx>
Christopher Faylor wrote:
> On Mon, Jul 18, 2005 at 08:21:09AM +0200, Mark Kettenis wrote:
>
>> Date: Sun, 17 Jul 2005 17:17:02 -0700
>> From: Mark Mitchell
>>
>> (1) Wait for readline-5.1 to be released, incorporate it into src/, and
>> then to add the minimal termcap stuff to a file in gdb/ that is only
>> used on MinGW.
>>
>> (2) I backport Chet's changes to rltty.c to the src/readline/
>> sourcebase, and then proceed as above. Because we know that these
>> changes will be in readline-5.1, we needn't worry overmuch about
>> divergence from upstread sources.
>>
>>You'll still need the minimal termcap stuff in gdb/ in this case isn't
>>it?
>
>
> Actually, I wonder if libiberty would be a better place for the minimal
> termcap stuff.
I knew someone would suggest that...
OK, I'll try that approach.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-07-18 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 0:17 Mark Mitchell
2005-07-18 0:23 ` Daniel Jacobowitz
2005-07-18 1:01 ` Christopher Faylor
2005-07-18 3:23 ` Eli Zaretskii
2005-07-18 6:22 ` Mark Kettenis
2005-07-18 14:13 ` Mark Mitchell
2005-07-18 14:35 ` Christopher Faylor
2005-07-18 14:34 ` Mark Mitchell [this message]
2005-07-18 16:55 ` Ian Lance Taylor
2005-07-18 17:10 ` Christopher Faylor
2005-07-18 17:26 ` Ian Lance Taylor
2005-07-18 17:33 ` Daniel Jacobowitz
2005-07-18 17:47 ` Christopher Faylor
2005-07-18 17:59 ` Mark Kettenis
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=42DBBDA8.5000602@codesourcery.com \
--to=mark@codesourcery.com \
--cc=chet.ramey@case.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=me@cgf.cx \
/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