From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Administrivia - is the download server ill?
Date: Mon, 12 May 2014 08:46:50 -0400 [thread overview]
Message-ID: <9450.1399898810@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
Seeing this the last few days trying to reach the repository:
% ping snapon.lab.bufferbloat.net
PING snapon.lab.bufferbloat.net (149.20.63.30) 56(84) bytes of data.
From int-0-0-1-0.r1.sql1.isc.org (149.20.65.10) icmp_seq=1 Destination Host Unreachable
^C
--- snapon.lab.bufferbloat.net ping statistics ---
10 packets transmitted, 0 received, +1 errors, 100% packet loss, time 9463ms
Hopefully it's just the hamsters escaped for the weekend and weren't
turning those wheels....
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next reply other threads:[~2014-05-12 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 12:46 Valdis Kletnieks [this message]
2014-05-12 20:07 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9450.1399898810@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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