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: Wed, 30 Oct 2002 15:30:21 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: inetd:ssh/telnet/ftp - Im too stupid to use these Message-ID: <20021030203021.GA12934@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <184670-2200210330202039402 AT M2W026 DOT mail2web DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <184670-2200210330202039402@M2W026.mail2web.com> User-Agent: Mutt/1.5.1i On Wed, Oct 30, 2002 at 03:20:39PM -0500, lhall AT pop DOT ma DOT ultranet DOT com 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/