From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] FYI: Mastersync is down
Date: Mon, 19 Mar 2018 21:13:37 -0400 [thread overview]
Message-ID: <CAAr7Pr_LvaAMZ2jZ4REaKVDSfSLMb12z7DEPX1EmuzZyJMZKkQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
This is just an FYI: https://infra-status.gentoo.org/
Hoping to have this fixed in a couple of days. In the meantime you may see
missing snapshots (for emerge webrsync) and no rsync propagation.
-A
[-- Attachment #2: Type: text/html, Size: 318 bytes --]
next reply other threads:[~2018-03-20 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 1:13 Alec Warner [this message]
2018-03-20 8:11 ` [gentoo-dev] About making mastersync redundant Fabian Groffen
2018-03-20 21:32 ` [gentoo-dev] Re: FYI: Mastersync is down Alec Warner
2018-03-20 22:22 ` Aaron Bauman
2018-03-21 1:11 ` Alec Warner
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=CAAr7Pr_LvaAMZ2jZ4REaKVDSfSLMb12z7DEPX1EmuzZyJMZKkQ@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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