From: Chris Faylor <cgf@cygnus.com>
To: cygwin <cygwin@sourceware.cygnus.com>
Subject: Re: CYGWIN: New version, B21, CD 1.0 ?
Date: Tue, 11 Apr 2000 04:55:00 -0000 [thread overview]
Message-ID: <20000411075548.B874@cygnus.com> (raw)
In-Reply-To: <036e01bfa38c$d41a3720$24313fc3@jtpc>
On Tue, Apr 11, 2000 at 09:06:23AM +0100, Joerg Troeger wrote:
>>>I think you should consider adding a few explanations about all of this
>>>on the web site (at least in the FAQ if not in the presentation or the
>>>first page).
>
>>We do. It says what the latest versions are. What more needs to be
>>said? Until we actually release something new, there isn't anything
>>really to say (outside the developers list, where this is all common
>>knowledge).
>
>What more? It would be nice and helpful and even worth the effort, to
>have some information about the state of a soon-to-be-coming release.
>
>"The eCos host tools and GNU development tools are dependent on the
>forthcoming full release of the Cygwin tools (scheduled 2000-04-07).
>It will not be possible to build eCos on Windows hosts prior to the
>release of the new Cygwin tools." (
> http://sourceware.cygnus.com/ecos/install-windows.html )
>
>For two weeks I am looking for this forthcoming full release of the
>Cygwin tools, which has been delayed for several times.
>
>What's about this release? The cygwin page doesn't mention it.
>
>It is interesting not only for developers, to get information about
>scheduled new releases. Should I join to the developer mailing list,
>to get this information?
The developers list is for people who are contributing to the cygwin
project.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-04-11 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 0:10 Joerg Troeger
2000-04-11 4:55 ` Chris Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-10 9:40 laurent.roche
2000-04-10 9:53 ` DJ Delorie
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=20000411075548.B874@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sourceware.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).