public inbox for
 help / color / mirror / Atom feed
From: (Frank Ch. Eigler)
Subject: IMPORTANT: hardware migration, MARCH 18..22
Date: Tue, 12 Mar 2013 15:43:00 -0000	[thread overview]
Message-ID: <20130312153605.40AC1581AC@fche.csb> (raw)

Hi -

Please be aware that **next week**, we will attempt to switch over the
hardware that serves and its aliases (,,, etc.) to newer & faster hardware
donated by Red Hat.

The plan is to take down network services next Monday around 14:00Z,
and gradually bring things back up on the new machine, one service at
a time, as quickly as possible.  Since this change involves switching
to a much younger OS and is complicated by many sourceware-specific
services, the overall outage may last up to several days.  We will
prioritize getting source code version control systems up first.

This announcement is being sent to those main mailing lists that have
been recently active; please feel free to share it.  You are welcome
to listen in on #overseers during the transition
period.  We appreciate your patience and hope that the new machines
will serve us all well.

- FChE

                 reply	other threads:[~2013-03-12 15:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130312153605.40AC1581AC@fche.csb \ \ \

* 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).