From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Is Cygwin 3.1.X Stable Enough to Use?
Date: Fri, 21 Feb 2020 21:34:00 -0000 [thread overview]
Message-ID: <97d019bd-48b9-4725-6a7f-9b4cec7f73f1@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAD8GWsvx7QM7+2FT-+yPMB+XHTt-TEx4pWhDs=fqA1PtuWMaVA@mail.gmail.com>
On 2020-02-21 07:26, Lee wrote:
> On 2/21/20, Paul Moore wrote:
>> On Fri, 21 Feb 2020 at 09:41, Takashi Yano wrote:
>>> On Thu, 20 Feb 2020 21:47:25 -0500, Lee wrote:
>>>> On 2/20/20, Lee wrote:
>>>>> I'll try backing out the registry change & see if it still happens.
>>>>
>>>> It doesn't happen now.
>>>>
>>>> I deleted HKEY_CURRENT_USER\Console\VirtualTerminalLevel
>>>> rebooted
>>>> deleted all the .o files under /source/tidy & rebuilt
>>>> The output of cmake looks normal
>>>>
>>>> I updated cygwin this morning:
>>>> 2020/02/20 07:49:28 Augmented Transaction List:
>>>> 2020/02/20 07:49:28 0 install cygwin 3.1.4-1
>>>> 2020/02/20 07:49:28 1 erase cygwin 3.1.2-1
>>>> 2020/02/20 07:49:28 2 install cygwin-devel 3.1.4-1
>>>> 2020/02/20 07:49:28 3 erase cygwin-devel 3.1.2-1
>>>>
>>>> is it possible that fixed it?
>>>
>>> I am not sure. In my environment the problem does not occur
>>> even with cygwin 3.1.2. Therefore, the cause cannot be identified.
>> I had the same issue and it was fixed by 3.1.4, so yes upgrading was
>> likely the fix.
> So, getting back to the OPs question about the stability of the
> current cygwin.. I'd say yes, it is "stable" now. The only problem
> I've seen doesn't happen after I upgraded and other pty issues seem to
> be closing fast
Check the git logs linked from the https://cygwin.com/snapshots/ page:
https://sourceware.org/git/?p=newlib-cygwin.git;a=shortlog
https://sourceware.org/git/?p=newlib-cygwin.git;a=log
and the patches mailing list archive:
https://cygwin.com/ml/cygwin-patches/current/threads.html
and you will see there is current activity which may be settled by the next
release 3.1.5.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2020-02-21 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 13:50 KARL BOTTS
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 [this message]
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=97d019bd-48b9-4725-6a7f-9b4cec7f73f1@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).