public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KARL BOTTS" <kdbotts@usa.net>
To: "cygwin" <cygwin@cygwin.com>
Subject: Is Cygwin 3.1.X Stable Enough to Use?
Date: Thu, 20 Feb 2020 13:50:00 -0000	[thread overview]
Message-ID: <817yBTNxU4176Set.1582206646@web03.cms.usa.net> (raw)


I am worried.  I need to instruct an IT department to install Cygwin.  I am
afraid that if I just tell them to run the installer, they will get an
unstable version.  I am afraid other new users will be in the same boat.

I am fine for myself: I am on Cygwin 3.07, it is a tank, and I can stay there
for the rest of the year if necessary.  That is not the issue.

Would it make sense for Disable_pcon (spelling?) to be the default, until the
new pty code settles down?

---
Karl Botts, kdbotts@usa.net


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

             reply	other threads:[~2020-02-20 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 13:50 KARL BOTTS [this message]
2020-02-20 18:50 ` Andrey Repin
2020-02-20 21:28   ` Lee
2020-02-21  0:20     ` Takashi Yano
2020-02-21  1:16       ` Brian Inglis
2020-02-21  1:27         ` Takashi Yano
2020-02-21  1:35           ` Brian Inglis
2020-02-21  1:50             ` Takashi Yano
2020-02-21  2:13               ` Lee
2020-02-21  2:01             ` Lee
2020-02-21  1:49       ` Lee
2020-02-21  2:06         ` Takashi Yano
2020-02-21  2:18           ` Lee
2020-02-21  2:47             ` Lee
2020-02-21  9:41               ` Takashi Yano
2020-02-21 11:13                 ` Paul Moore
2020-02-21 14:26                   ` Lee
2020-02-21 21:34                     ` Brian Inglis

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=817yBTNxU4176Set.1582206646@web03.cms.usa.net \
    --to=kdbotts@usa.net \
    --cc=cygwin@cygwin.com \
    /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).