From: dahms@ifk20.mach.uni-karlsruhe.de
To: fjh@cs.mu.OZ.AU
Cc: gnu-win32@cygnus.com, dahms@ifk20.mach.uni-karlsruhe.de
Subject: Re: Feedback needed on proposed cygwin feature
Date: Tue, 02 Dec 1997 16:54:00 -0000 [thread overview]
Message-ID: <009BE319.3FA64320.29436@ifk20.mach.uni-karlsruhe.de> (raw)
Hi Fergus, you wrote:
: I don't see any good reason to hard-code the `32'.
:
: Using `CYGWIN32' won't look very good on say the 64-bit NT Alpha port.
MS should have made the jump to >32bit at NT4, at a time several other
unices already were 64bit, and provide a real useful POSIX before forcing
all of us to NT, saving all this hassle!
Bye, Heribert (dahms@ifk20.mach.uni-karlsruhe.de)
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-12-02 16:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 16:54 dahms [this message]
1997-12-03 7:38 ` Theodore Jump
-- strict thread matches above, loose matches on Subject: below --
1997-12-04 17:09 Chris Faylor
1997-12-04 17:07 Michael Anthon
1997-12-05 8:07 ` Chris Faylor
1997-12-02 20:23 Earnie Boyd
1997-12-02 9:41 marcus
1997-12-03 6:00 ` Tomas Fasth
1997-12-03 18:36 ` Chris Faylor
1997-12-04 13:02 ` Tomas Fasth
1997-12-05 8:07 ` Chris Faylor
1997-12-03 7:38 ` Chris Faylor
1997-12-02 7:22 Chris Faylor
1997-12-02 6:11 Chris Faylor
1997-12-01 22:51 Chris Faylor
1997-12-01 22:51 ` Jason Zions
1997-12-01 22:51 Chris Faylor
1997-12-01 11:43 JONCKHEERE
1997-12-02 7:23 ` Chris Faylor
1997-12-01 5:09 Earnie Boyd
1997-12-01 2:03 Chris Faylor
1997-12-01 9:09 ` Norm Peterson
1997-12-01 11:47 ` Jason Zions
1997-12-01 22:10 ` Justin Smith
1997-12-01 22:51 ` Theodore Jump
1997-12-01 22:51 ` Michael Hirmke
1997-12-02 7:16 ` Chris Faylor
1997-12-02 9:41 ` Fergus Henderson
1997-12-03 7:38 ` Chris Faylor
1997-12-02 5:17 ` Kimon Kontovasilis
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=009BE319.3FA64320.29436@ifk20.mach.uni-karlsruhe.de \
--to=dahms@ifk20.mach.uni-karlsruhe.de \
--cc=fjh@cs.mu.OZ.AU \
--cc=gnu-win32@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).