This is the mail archive of the
mailing list for the Cygwin project.
Re: Question about old win32 api
- From: Michael Enright <mike at kmcardiff dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 21 Sep 2015 17:04:20 -0700
- Subject: Re: Question about old win32 api
- Authentication-results: sourceware.org; auth=none
- References: <A8FCEC4C682E094AAB49CE0CE41E28EA18502B88 at EXCHMB06 dot is dot l-3com dot com> <1442854377 dot 11704 dot 18 dot camel at cygwin dot com> <A8FCEC4C682E094AAB49CE0CE41E28EA18502C2E at EXCHMB06 dot is dot l-3com dot com> <1195136399 dot 20150921222509 at yandex dot ru> <CAOC2fq-WaBg1aug_iG92Z3B7PvYD+EmpsWhCdS7HHDW0JZMijQ at mail dot gmail dot com> <5600691F dot 2090204 at gmail dot com>
On Mon, Sep 21, 2015 at 1:31 PM, Marco Atzeri wrote:
> the change in nc had nothing to do with cygwin
> change between 1.5 and 1.7
Implying a tie between the nc version to the release of 1.7.0-0 was
wrong on my part. I am not wrong in this change to 'nc' did happen.
Because I was not tracking all things Cygwin all the time I didn't
know about it at first, and the people who had problems with it in my
world were those who had deployed new workstations with Cygwin 1.7
while those who could just keep using Cygwin 1.5 did not have
problems. The point is that Cygwin doesn't stay the same all the time
in the ways that all users may care about.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple