From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Frank Ch. Eigler" <fche@redhat.com>,
Sourceware Overseers <overseers@sourceware.org>,
Jonathan Larmour <jifl@jifvik.org>
Subject: Re: sourceware hardware transition
Date: Wed, 13 Mar 2013 17:26:00 -0000 [thread overview]
Message-ID: <20130313172629.GB7340@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20130313172238.GD11197@redhat.com>
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
next prev parent reply other threads:[~2013-03-13 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 21:29 Frank Ch. Eigler
2013-03-11 21:43 ` Jeff Law
2013-03-11 21:58 ` Jeff Law
2013-03-11 23:20 ` Christopher Faylor
2013-03-12 5:25 ` Ian Lance Taylor
2013-03-13 6:36 ` Jonathan Larmour
2013-03-13 17:23 ` Frank Ch. Eigler
2013-03-13 17:26 ` Christopher Faylor [this message]
2013-03-20 1:41 ` Gerald Pfeifer
2013-03-20 2:19 ` Christopher Faylor
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=20130313172629.GB7340@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=fche@redhat.com \
--cc=jifl@jifvik.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).