delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-Id: | <5.1.0.14.2.20020315013124.00aa5150@mail.earthlink.net> |
X-Sender: | felixmendelssohnn AT mail DOT earthlink DOT net |
X-Mailer: | QUALCOMM Windows Eudora Version 5.1 |
Date: | Fri, 15 Mar 2002 01:33:06 -0500 |
To: | cygwin AT cygwin DOT com |
From: | felixmendelssohnn AT mail DOT earthlink DOT net |
Subject: | cygwin.com suggestions |
Mime-Version: | 1.0 |
Here are a couple of suggestions for making the cygwin.com website more helpful. 1) Include the current version number of setup.exe on the front page. Otherwise, there is no way for the infrequent visitor to the website to know if setup.exe has been updated other than to re-download and run it. 2) Include in the FAQ (or somewhere) a section on "How to Safely Update the Cygwin dll". Probably just "shut down all cygwin apps, including daemons", but it would be useful to know for sure. 3) Include or link those instructions in announcements of new Cygwin dll releases. Do these make sense? Jeremy -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |