From: David Starks-Browning <starksb@ebi.ac.uk>
To: cygwin@cygwin.com
Subject: RE: Is the Cygwin 1.3.2 DLL Win 2000 compatible?
Date: Sun, 03 Mar 2002 00:54:00 -0000 [thread overview]
Message-ID: <3578-Sun03Mar2002085418+0000-starksb@ebi.ac.uk> (raw)
In-Reply-To: <4.3.1.2.20020301110418.0243f488@pop.ma.ultranet.com>
On Friday 1 Mar 02, Larry Hall (RFK Partners, Inc) writes:
> Perhaps. It's an esoteric one. The original poster of this question wanted
> to know if Cygwin 1.3.2 would work with Win2000. I replied with the FAQ
> entry that says Cygwin works with 9x/Me/NT/W2K/XP. The reply I got back
> from the poster then was that he had seen this entry but thought it
> referenced only the current Cygwin DLL (1.3.9 at that point). So the only
> question I was raising was whether you think it would be more or less
> confusing to people to add some wording to the FAQ entry that specifies
> that any recent Cygwin DLL works with Windows, not just the latest.
> It's not clear to me that this additional wording wouldn't raise more
> questions than it answers. Judging by your response, I think leaving things
> as is may be the best option. What do you think?
I think it's best to leave this entry as it is.
Thanks,
David
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-03-03 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <570DA4A1BC7DD4119AD7000629551498013E10E1@pjmnt11.pjm.com>
2002-02-28 17:00 ` Larry Hall (RFK Partners, Inc)
2002-03-01 5:00 ` David Starks-Browning
2002-03-01 8:19 ` Larry Hall (RFK Partners, Inc)
2002-03-03 0:54 ` David Starks-Browning [this message]
2002-03-04 7:26 ` Larry Hall (RFK Partners, Inc)
2002-02-28 14:50 jonesr
2002-02-28 16:03 ` Larry Hall (RFK Partners, Inc)
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=3578-Sun03Mar2002085418+0000-starksb@ebi.ac.uk \
--to=starksb@ebi.ac.uk \
--cc=cygwin@cygwin.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).