From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20435 invoked by alias); 13 Mar 2013 17:26:42 -0000 Received: (qmail 20399 invoked by uid 22791); 13 Mar 2013 17:26:41 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mho-03-ewr.mailhop.org (HELO mho-01-ewr.mailhop.org) (204.13.248.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 Mar 2013 17:26:34 +0000 Received: from pool-108-20-146-82.bstnma.fios.verizon.net ([108.20.146.82] helo=cgf.cx) by mho-01-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1UFpRf-000ESh-3J; Wed, 13 Mar 2013 17:26:31 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id AC15588041D; Wed, 13 Mar 2013 13:26:29 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/KRscSpqHte6s75L12GYUc Date: Wed, 13 Mar 2013 17:26:00 -0000 From: Christopher Faylor To: "Frank Ch. Eigler" , Sourceware Overseers , Jonathan Larmour Subject: Re: sourceware hardware transition Message-ID: <20130313172629.GB7340@ednor.casa.cgf.cx> Mail-Followup-To: "Frank Ch. Eigler" , Sourceware Overseers , Jonathan Larmour References: <20130311212918.GF3288@redhat.com> <51401E6A.7040709@jifvik.org> <20130313172238.GD11197@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130313172238.GD11197@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2013-q1/txt/msg00088.txt.bz2 On Wed, Mar 13, 2013 at 01:22:38PM -0400, Frank Ch. Eigler wrote: >Hi - > >On Wed, Mar 13, 2013 at 07:36:26AM +0100, Jonathan Larmour wrote: >> [...] >> Since at least gcc bugzilla relies on things like bugzilla mail handling, >> including some magic scripts relating commits to bugs; and every project >> has some sort of mailing list for commits, I think things will need >> firewalling before the hordes. > >There is a tradeoff here. I suspect it's more acceptable to get >version control systems up ASAP (and risk losing some VCS- or >bugzilla-notification emails), than delay bringing the machine up >until all those interdependent services are up. What do you think? I don't know. In the past people have been upset when email like this goes missing. I could probably get email working well enough to work with this but I don't know enough about bugzilla to confidently predict what's needed there. Could we have our bugzilla guy on tap for this event? cgf