Re: Question about old win32 api

[Vince Rice <vrice at solidrocksystems dot com>]

> On Sep 21, 2015, at 7:04 PM, Michael Enright <mike@kmcardiff.com> wrote:
> 
> 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
>> 
>> https://sourceware.org/ml/cygwin-announce/2012-05/msg00015.html
>> 
> 
> 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.

It did happen, and as Marco pointed out, it was _announced_ that
it happened. If someone is using Cygwin, not following the mailing
list (at the very least the announce list), and updating the software
blindly, then there's not much else to be done. They're almost
guaranteed to run into problems.

This is no different than any other software on the planet â
blindly updating Linux versions without knowing whatâs in the
update, or blindly updating Word without knowing whatâs in
the update, and so on, leads to the same thing â problems
can, and will, happen.
--
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