From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@cygnus.com
Cc: DJ Delorie <dj@delorie.com>, shebs@cygnus.com, robert.hoehne@gmx.net
Subject: Re: Two patches for the readline lib
Date: Mon, 15 Mar 1999 11:48:00 -0000 [thread overview]
Message-ID: <36ED63EB.54B1@cygnus.com> (raw)
In-Reply-To: <199903142206.OAA18440@cygnus.com>
Robert Hoehne wrote:
>
> The following patches for readline disable some terminal specific
> code which is not available for DJGPP.
In that case, would it be appropriate to use a single macro
(eg. if defined (__DJGPP__)) to control these changes? The old
readline was a hodge-podge of different ifdefs of this sort.
It'd be nice to keep it under control this time.
q
WARNING: multiple messages have this Message-ID
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@cygnus.com
Cc: DJ Delorie <dj@delorie.com>, shebs@cygnus.com, robert.hoehne@gmx.net
Subject: Re: Two patches for the readline lib
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <36ED63EB.54B1@cygnus.com> (raw)
Message-ID: <19990401000000.KMVXuDw_ZVEF2Rd8M6U1YbCcEYpujxUk9qfBL0AkXYU@z> (raw)
In-Reply-To: <199903142206.OAA18440@cygnus.com>
Robert Hoehne wrote:
>
> The following patches for readline disable some terminal specific
> code which is not available for DJGPP.
In that case, would it be appropriate to use a single macro
(eg. if defined (__DJGPP__)) to control these changes? The old
readline was a hodge-podge of different ifdefs of this sort.
It'd be nice to keep it under control this time.
q
next prev parent reply other threads:[~1999-03-15 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 14:41 Robert Hoehne
1999-03-15 11:48 ` Michael Snyder [this message]
1999-04-01 0:00 ` Robert Hoehne
1999-03-15 14:04 ` Robert Hoehne
1999-04-01 0:00 ` Michael Snyder
1999-04-01 0:00 ` DJ Delorie
1999-03-16 11:09 ` DJ Delorie
1999-04-01 0:00 ` Elena Zannoni
1999-03-23 9:54 ` Elena Zannoni
1999-04-01 0:00 ` Robert Hoehne
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=36ED63EB.54B1@cygnus.com \
--to=msnyder@cygnus.com \
--cc=dj@delorie.com \
--cc=gdb-patches@cygnus.com \
--cc=robert.hoehne@gmx.net \
--cc=shebs@cygnus.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