public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: Spurious / persistent "exception" condition in half-closed sockets
Date: Sat, 9 Jul 2022 23:02:34 +0000	[thread overview]
Message-ID: <DM8PR09MB709579155BA92F3E3A43039BA5859@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <649314d9-4862-af2d-3717-2809b818a820@cornell.edu>

> This was fixed in Cygwin 3.3.0, as the announcement of the latter stated:

Thanks!  So maybe it is time to upgrade... after all LOL

> But you can still run a parallel Cygwin installation

I tried that before...  And it did not work out well.  Unless it's a VM,
there's a small but real chance that at some point they are to get intertwined,
and then ... it's quite a mess (learned that the hard way, unfortunately).

Anton Lavrentiev
Contractor NIH/NLM/NCBI


  reply	other threads:[~2022-07-09 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 15:37 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-09 21:05 ` Ken Brown
2022-07-09 23:02   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-07-11  7:52     ` [EXTERNAL] " Corinna Vinschen
2022-07-11  8:16       ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM8PR09MB709579155BA92F3E3A43039BA5859@DM8PR09MB7095.namprd09.prod.outlook.com \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@cygwin.com \
    --cc=kbrown@cornell.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).