DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:subject:mime-version:content-type
	:content-transfer-encoding:date:from:message-id; q=dns; s=
	default; b=frg8dslCbxEPVgRXq1CANMIwjmevyJVerv/DCqNjqCI2WFRvTCYrK
	kJPeRuK5eK1nJZENBNnxo+pOzhBlr8YnEYlMoXu6f2GLrN/I7gafgNz6w/ayOFPV
	vIqUK84DVRwF4gIrhGrWm2x7NrjIkiYLDcuZOTmP38oXbOmMC2HFU4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Re: Problem with line buffering and getc function on 1.7.33.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Date: Fri, 11 Mar 2016 13:57:52 -0800
From: Kaz Kylheku <920-082-4242@kylheku.com>
Message-ID: <a0c23290b3a8502552dcf149fbfa5f90@mail.kylheku.com>
User-Agent: Roundcube Webmail/0.9.2
Content-Transfer-Encoding: 8bit

On 11.03.2016 12:08, Yaakov Selkowitz wrote:
> On 2016-03-11 13:16, Kaz Kylheku wrote:
> 
>> On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered an 
>> odd issue.
> 
> This is a 15-month old release which is no longer supported. Please
> update to 2.4.1.

Do you mean, "Please update to 2.4.1, it is fixed there!"
or do you mean "You haven't done enough with that minimal
C repro case; please keep investigating against
the latest code?"

I'm not looking for support for old versions of Cygwin.
My program *is* supported for users who have that
15-month-old version, and I can provide that support
entirely by myself, as you can see.

There is no benefit to me in reporting this issue
at all, since the workaround is acceptable and will
likely keep working indefinitely.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple