Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.1.2.0.20050712103021.09a9a4b8@pop.prospeed.net>
Date: Tue, 12 Jul 2005 10:54:33 -0400
To: Amadeus Stevenson <amadeus DOT stevenson AT gmail DOT com>, cygwin AT cygwin DOT com
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: Brief, simple guide to cygwin
In-Reply-To: <1c42f0e05071203536bbdc3c2@mail.gmail.com>
References: <1c42f0e05071203536bbdc3c2 AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 06:53 AM 7/12/2005, you wrote:
>I updated a brief guide to cygwin on my website.
>
>"Setting up 'cygwin' as a UNIX shell script editing environment on Windows."
>
>http://poff.sixbit.org/content/cygwin
>
>All the information is gleaned from faqs/man pages and experience.
>

<snip>


>If anyone has any +/- comments then feel free to contact me. 


I assume that this statement applies equally to the part that I'm quoting
so here are my comments.  This list isn't in the habit of reviewing 
off-site Cygwin guides.  While you certainly have the freedom to post such 
an external guide to this list, we only recommend people using Cygwin use 
the Cygwin site (www.cygwin.com) and package documentation (generally under 
/usr/share/doc/Cygwin) as guides to installing, configuring, and using 
Cygwin and it's tools.  This is because we cannot be responsible for 
supporting and keeping off-site guides accurate and up-to-date.  We receive 
regular inquiries on this list from people who have used such off-site 
guides to configure some Cygwin utility and are suffering for it.  When this 
happens, we're forced to recommend one of two courses of action - contact 
the owner of the guide for support on the issue or uninstall the 
affected package(s), reinstall, and configure them using the Cygwin 
documentation and configure scripts.

If you feel there is something missing from the available documentation at 
the Cygwin site or in one of the supplied packages, we'd prefer that you 
try to get this shortcoming addressed within the existing docs, rather 
than creating other docs and placing them elsewhere on the net.  You can do 
this by posting your observation or concern to this list or, better yet, 
provide a patch to the appropriate doc with your suggested wording.

I will say that I took a quick look at your site and what you've written 
there.   While there are definitely some correct instructions there 
pertaining to Cygwin, there are also incorrect and misleading ones.  So 
for this and all of the reasons I've mentioned above, the Cygwin site won't
be recommending or offering to help people who use it and have any problems 
or questions.  I hope this isn't different than your expectations when you
originally posted.

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/