From: Eli Zaretskii <eliz@gnu.org>
To: "Mark E." <snowball3@bigfoot.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: DOS/Windows-related changes in the include subdirectory
Date: Tue, 07 Sep 1999 05:54:00 -0000 [thread overview]
Message-ID: <199909071254.IAA01790@mescaline.gnu.org> (raw)
In-Reply-To: <199909061722.NAA15568@mescaline.gnu.org>
> > If you want me to change the definitions, please send me the
> > definitions from the GCC sources (I don't have them installed).
>
> Since I'm responsible for the above mentioned GCC changes, I can
> help you Eli if you are going to make the changes.
It's up to Ian. If he wants me to change the macros to make them more
close to what GCC uses, I will do it. I used these macros (with minor
changes, as the case in point might dictate) in quite a few packages
that now include them in official GNU releases, although GCC is
obviously not one of them.
next prev parent reply other threads:[~1999-09-07 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 1:14 Eli Zaretskii
1999-09-06 8:10 ` Ian Lance Taylor
1999-09-06 10:22 ` Eli Zaretskii
1999-09-06 10:31 ` Ian Lance Taylor
1999-09-06 11:20 ` Mark E.
1999-09-07 5:54 ` Eli Zaretskii [this message]
1999-09-07 5:49 ` Eli Zaretskii
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=199909071254.IAA01790@mescaline.gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.cygnus.com \
--cc=snowball3@bigfoot.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).