From: "E. Madison Bray" <erik.m.bray@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
Date: Wed, 27 Feb 2019 16:17:00 -0000 [thread overview]
Message-ID: <CAOTD34YOqRDNJiuD2A93WyT98wVWie=E-+x2Tc+SykSOTAwMzg@mail.gmail.com> (raw)
In-Reply-To: <5c7607bb.1c69fb81.ce2c0.65ce@mx.google.com>
On Wed, Feb 27, 2019 at 4:45 AM Steven Penny wrote:
>
> On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote:
> > Well I guess it's a good thing there's only one possible state of
> > Windows 7 x64 which allows us to determine that there's no possibility
> > of a bug simply by running a single instance in one VM. We're going to
> > turn the world of unit testing on its ear with this information.
>
> correct, multiple states are possible. this is why the scientific method defines
> a control:
>
> https://wikipedia.org/wiki/Scientific_control
>
> in this case that would be a clean virtual machine. if you cant or wont do that,
> then you must understand that you only have yourself to blame.
I understand this thread has been heated, and it hasn't been just you
who's been impatient by any means. But maybe it will help smooth
things over by avoiding words like "blame" and finger pointing. If
someone has a broken Cygwin on their system that works on other,
similar systems it's not necessarily the user who's to "tlame".
Yes, PEBKAC is always a possibility, but since you mentioned the
scientific method I'll just add that we have no evidence of that
either. Windows, much someone's working installation of Windows
(which can have a lot more going on on it than a fresh VM) is an
enormously complex system, and it's entirely possible that Cygwin is
*broken* on that particular configuration through no fault of the
user.
Unfortunately, without concrete steps to reproduce the problem, the
rest of us can only speculate.
--
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
next prev parent reply other threads:[~2019-02-27 15:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:28 Jerry Baker via cygwin
2019-02-26 18:30 ` Jerry Baker via cygwin
2019-02-26 18:38 ` Houder
2019-02-26 18:44 ` Jerry Baker via cygwin
2019-02-26 18:45 ` Richard Campbell
2019-02-26 18:59 ` Vince Rice
2019-02-26 19:19 ` Jerry Baker via cygwin
2019-02-26 19:32 ` Ken Brown
2019-02-26 20:00 ` Jerry Baker via cygwin
2019-02-26 20:42 ` Jerry Baker via cygwin
2019-02-26 21:09 ` Vince Rice
2019-02-26 22:10 ` Doug Henderson
2019-02-26 22:19 ` Jerry Baker via cygwin
2019-02-26 22:48 ` Jerry Baker via cygwin
2019-02-26 23:00 ` Doug Henderson
2019-02-27 0:50 ` Jerry Baker via cygwin
2019-02-27 1:50 ` Steven Penny
2019-02-27 2:01 ` Jerry Baker via cygwin
2019-02-27 2:43 ` Jerry Baker via cygwin
2019-02-27 3:21 ` Doug Henderson
2019-02-27 3:45 ` Jerry Baker via cygwin
2019-02-27 6:55 ` Houder
2019-02-27 2:56 ` Steven Penny
2019-02-27 3:05 ` Jerry Baker via cygwin
2019-02-27 3:12 ` Steven Penny
2019-02-27 3:27 ` Jerry Baker via cygwin
2019-02-27 5:11 ` Steven Penny
2019-02-27 16:17 ` E. Madison Bray [this message]
2019-02-27 5:57 ` Vince Rice
2019-02-27 7:26 ` Brian Inglis
2019-02-27 20:23 ` Jerry Baker via cygwin
2019-02-27 20:27 ` Jerry Baker via cygwin
2019-02-27 20:50 ` Jerry Baker via cygwin
2019-02-27 21:48 ` Corinna Vinschen
2019-02-28 3:12 ` Jerry Baker via cygwin
2019-02-28 9:39 ` L A Walsh
2019-02-28 10:52 ` Corinna Vinschen
2019-03-11 21:27 ` Bill Stewart
2019-03-11 21:38 ` Achim Gratz
2019-03-11 21:46 ` Bill Stewart
2019-03-12 0:20 ` Andrey Repin
2019-02-27 20:44 ` Eric Blake
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='CAOTD34YOqRDNJiuD2A93WyT98wVWie=E-+x2Tc+SykSOTAwMzg@mail.gmail.com' \
--to=erik.m.bray@gmail.com \
--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).