From: Aaron Bauman <bman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: FYI: Mastersync is down
Date: Tue, 20 Mar 2018 18:22:50 -0400 [thread overview]
Message-ID: <20180320222250.GB18760@monkey> (raw)
In-Reply-To: <CAAr7Pr8mL1d6YCXqcCvwk3_z+BL26gxp=egBfXhxEFnfjUX5KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Tue, Mar 20, 2018 at 05:32:23PM -0400, Alec Warner wrote:
> Disk maintenance is ongoing from now for +2h while we swap disks.
>
> Because I'm pessimistic, I expect funny business during the swap; so
> maintenance may extend further out.
>
> If all goes well, the disks in the new hardware should be a good fit and
> master-rsync should return to service after the maintenance.
>
> -A
Thank you for your dedicated work, Alec :)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-20 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 1:13 [gentoo-dev] FYI: Mastersync is down Alec Warner
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 [this message]
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=20180320222250.GB18760@monkey \
--to=bman@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