Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 15 Jul 2004 10:01:56 +1000 (EST) From: luke DOT kendall AT cisra DOT canon DOT com DOT au Subject: Re: /usr/share/doc/Cygwin (Was Re: sending email from Cygwin) To: cygwin AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20040715000156.81C6084C1E@pessard.research.canon.com.au> On 14 Jul, Igor Pechtchanski wrote: > Yep, that would be a very good idea. In particular, it should point out > that the information in the READMEs in /usr/share/doc/Cygwin takes > precedence over that in the package READMEs and manpages. > > Maybe even an FAQ entry like "I've followed directions in the README / man > page / info file to the letter, and still can't get the package to work - > what gives?" (put in this form, it *is* rather frequently asked). :-) Can I also suggest that the FAQ's section called "Where can I get more information? / Where's the documentation?" would be an excellent place to mention that all the per-package readme files are collected together in /usr/share/doc/Cygwin? That would be where I'd look first to try to discover the info. Regards, luke -- 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/