Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <3B9E4F0C.8020705@ece.gatech.edu>
Date: Tue, 11 Sep 2001 13:51:08 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Possible (new) sscanf bug
References: <3B9E11CF.3010407@ece.gatech.edu> <20010911111316.D12667@redhat.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

> I've forwarded this to the newlib mailing list.
> 
> sscanf is not in cygwin's domain.  It's maintained by another group.
> 


Yeah, I know.  I just figured the cygwin list should be aware of this 
*possible* bug given the current 1.3.3 work.  You are correct -- newlib 
is the correct list.  I probably should have cross-posted to both, and 
asked that replies be directed to newlib only.  Oh well.

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