Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <3C914380.9020508@ece.gatech.edu>
Date: Thu, 14 Mar 2002 19:42:40 -0500
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
CC: cygwin@cygwin.com
Subject: Re: Having problems with sshd and user accounts?  1.3.10    appears to be broken, 1.3.9 fixed it...
References: <a6qeii$49m$1@main.gmane.org> <4.3.1.2.20020314101743.01ca4ff0@pop.ma.ultranet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Larry Hall (RFK Partners, Inc) wrote:

> Thank goodness someone has found the Cygwin release that's a panacea for all 
> subsequent Cygwin ills!  I'd heard B20 touted as this for so long that I was
> afraid Cygwin would never reach such heights again.  Boy am I relieved!  I 
> guess there's no need for further Cygwin releases, since 1.3.9 is now the 
> cure all (actually, this makes me wonder why there were any releases after 
> B20....)  Anybody have any idea what would be a good use of the newly freed 
> up time of members of this group?


LOL!

Although, the XEmacs-centric crowd has been recommending "stay at 1.3.2" 
for some time, now. So unfortunately, 1.3.9 is NOT a complete panacea. 
We *may* actually have to keep developing cygwin...mebbe 1.3.11 will be 
all the juicy goodness of 1.3.2 + 1.3.9, and then we can stop?

--Chuck



--
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/

