Yep. I agree it's important to keep focused on the goal here. If the information at external sites pointed to by this list is wrong, incomplete, or out-of-date, this helps no one and the Cygwin community doesn't have any direct action it can take to correct the data point. Keeping the information within the project, this information can be corrected directly as required by the Cygwin community. That helps everyone. What's not to like? ;-)
Larry Original Message: ----------------- From: Christopher Faylor [EMAIL PROTECTED] Date: Wed, 30 Oct 2002 15:30:21 -0500 To: [EMAIL PROTECTED] Subject: Re: inetd:ssh/telnet/ftp - Im too stupid to use these On Wed, Oct 30, 2002 at 03:20:39PM -0500, [EMAIL PROTECTED] wrote: >Perhaps this makes sense as a step in the process but it can't be the >end-game if folks really want to make the process easier for everyone. >I'm not against any steps necessary if it improves any part of Cygwin >but unless the improvement actually folds into the final product >(Cygwin itself) as Chris points out, various disjointed and >disconnected solutions will likely lead to more confusion and problems >in the future. It's worth thinking about for anyone that's taken the >first step. This stuff can all be helpful. Let's try to get it all in >one place! :-) In this case the information provided could possibly be considered more confusing than what is already available, too. So, submitting documentation for review and incorporation would theoretically weed out the confusing or incorrect parts. cgf -- 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/ -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . -- 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/
