From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: Redhat, Sourceware, Cygwin Web Site Outage Recovering
Date: Fri, 21 Apr 2017 21:59:00 -0000 [thread overview]
Message-ID: <0cc638b1-1dbc-29c8-f366-b35b1e7f941f@Shaw.ca> (raw)
In-Reply-To: <db008e58-05d0-1121-eba3-4ebe18900590@benkamen.net>
On 2017-04-21 12:37, Ben Kamen wrote:
> On 04/21/2017 01:30 PM, Brian Inglis wrote:
>> Looks like Redhat, Sourceware, Cygwin web sites are coming
>> back up after an outage (confirmed by two isup/down sites) or
>> there have been some major network issues on the west coast
>
> I wonder if it was west-coast...
>
> I had issues getting to some Xilinx FPGA resources this morning....
Power outage hit 90k SFO FiDi customers - could have some impact?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2017-04-21 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 19:29 Brian Inglis
2017-04-21 20:39 ` Ben Kamen
2017-04-21 21:59 ` Brian Inglis [this message]
2017-04-21 22:30 ` david
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=0cc638b1-1dbc-29c8-f366-b35b1e7f941f@Shaw.ca \
--to=brian.inglis@shaw.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).