From: dahms@ifk20.mach.uni-karlsruhe.de
To: eric@osiris.com.au
Cc: gnu-win32@cygnus.com, dahms@ifk20.mach.uni-karlsruhe.de
Subject: Re: bash env parse broken
Date: Tue, 09 Sep 1997 23:33:00 -0000 [thread overview]
Message-ID: <009BA112.B60C62E0.22937@ifk20.mach.uni-karlsruhe.de> (raw)
Hi Eric, you wrote:
: find that the power up time for bash is somewhere between 5 and 10 times
: longer on NT + cygwin32 than UNIX for the identical hardware.
: Would anyone care to comment on where the cycles are going?
Sacrificed to Bill G's because of the unusable Posix subsystem 8-)
Has anyone benchmarks for the same H/W running cygwin/UWIN/OpenNT/NutCracker?
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-09-09 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-09 23:33 dahms [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-10 1:50 Bryan T. Schmersal
1997-09-09 16:24 dahms
1997-09-08 19:18 Eric Mills
1997-09-09 0:16 ` Alex
1997-09-02 15:50 Eric Mills
1997-09-04 12:06 ` Aaron P. Siri
1997-09-04 21:18 ` Chet Ramey
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=009BA112.B60C62E0.22937@ifk20.mach.uni-karlsruhe.de \
--to=dahms@ifk20.mach.uni-karlsruhe.de \
--cc=eric@osiris.com.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).