Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: ian@airs.com
Cc: me@cgf.cx, mark@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: Guidance re. MinGW and readline
Date: Mon, 18 Jul 2005 17:59:00 -0000	[thread overview]
Message-ID: <200507181758.j6IHwCfM017492@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <m3fyuc12bg.fsf@gossamer.airs.com> (message from Ian Lance Taylor on 18 Jul 2005 09:55:31 -0700)

   From: Ian Lance Taylor <ian@airs.com>
   Date: 18 Jul 2005 09:55:31 -0700

   Christopher Faylor <me@cgf.cx> writes:

   > Actually, I wonder if libiberty would be a better place for the minimal
   > termcap stuff.

   I don't see why, unless we seriously think that some program other
   than gdb is going to want to use it.  If I understand the earlier
   messages, the only point to the minimal termcap stuff is to use it
   with readline on MinGW.  That seems fairly special purpose to me, and
   not the sort of thing we usually put it into libiberty.

I agree with Ian here.  We should not add the additional burden of
maintining this both trees unless there actually is a benefit.

Mark


      parent reply	other threads:[~2005-07-18 17:59 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
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 [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=200507181758.j6IHwCfM017492@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ian@airs.com \
    --cc=mark@codesourcery.com \
    --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