From: Geoffrey Noer <noer@cygnus.com>
To: Darren Evans <darren@onlinemagic.com>, gnu-win32@cygnus.com
Subject: Re: Future of Cygwin32
Date: Wed, 29 Jul 1998 05:58:00 -0000 [thread overview]
Message-ID: <19980729001315.A4014@cygnus.com> (raw)
In-Reply-To: <3.0.5.32.19980728121312.00a7bc60@mailhost.onlinemagic.com>
> Im curious what features will be in the next version of Cygnus and when
> it's due? I seem to recall someone saying, when x returns from Holiday,
> but that was a while ago ..
>
> Heres my wishlist:
> Complete with egcs
> Upto date tools :)
> Paths stored in registry for cygnus and egcs
> and so on ..
I don't have a firm feature list yet or a date. That said, we are
aiming to make a new release as soon as it makes sense. We're in the
middle of Cygwin32 performance optimizations right now so we are
waiting until Cygwin32 is well-tested again and ready for another
release. Windows 98 support will be present. Hopefully, EGCS 1.1
will be included as the compiler. I will let everyone know when we
know more.
I am looking into upgrading sed to 3.01 but I don't expect that it
will make that big of a difference in configure times. (Hopefully
I'm wrong). Linux has the advantage that I/O appears to be much
faster on ext2 partitions. If you compare Linux running on a fat
filesystem to NT on the same, a lot of the performance difference goes
away...
--
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1998-07-29 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-24 12:58 sed 3.01 is many times faster than 2.05 under B19.1/Win95 Pavel Roskin
1998-07-28 5:54 ` Future of cygnus Darren Evans
1998-07-29 5:58 ` Geoffrey Noer [this message]
1998-07-31 3:03 ` Future of Cygwin32 Darren Evans
1998-07-31 2:45 Charles Randall
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=19980729001315.A4014@cygnus.com \
--to=noer@cygnus.com \
--cc=darren@onlinemagic.com \
--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).