From: Keir Fraser <keir.xen@gmail.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <dunlapg@umich.edu>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"keir@xen.org" <keir@xen.org>
Subject: Re: [PATCH v2 4/4] Clone and build Seabios by default
Date: Fri, 09 Sep 2011 12:23:59 +0100 [thread overview]
Message-ID: <CA8FB5DF.20905%keir.xen@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109091146260.12963@kaball-desktop>
On 09/09/2011 11:46, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com>
wrote:
>> But that means that if the sites hosting ipxe or qemu go down, people
>> can't build Xen. Keeping a copy on xen.org removes external
>> dependencies we don't have any control over.
>
> AKA single point of failure?
Better than multiple independent points of failure.
However, we already depend on the upstream ipxe site. Changing over to all
downloads from a single site under our control would be a separate issue and
patch, imo.
-- Keir
next prev parent reply other threads:[~2011-09-09 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 17:47 [PATCH v2 1/4] Move the ioemu-dir-find shell script to an external file stefano.stabellini
2011-09-08 17:47 ` [PATCH v2 2/4] Rename ioemu-dir as qemu-xen-traditional-dir stefano.stabellini
2011-09-08 17:47 ` [PATCH v2 3/4] Clone and build upstream Qemu by default stefano.stabellini
2011-09-08 17:56 ` Ian Campbell
2011-09-09 10:18 ` Stefano Stabellini
2011-09-09 13:59 ` Ian Campbell
2011-09-09 14:31 ` Ian Campbell
2011-09-09 16:43 ` Stefano Stabellini
2011-09-09 17:18 ` Ian Campbell
2011-09-08 17:47 ` [PATCH v2 4/4] Clone and build Seabios " stefano.stabellini
2011-09-08 18:00 ` Ian Campbell
2011-09-09 10:19 ` Stefano Stabellini
2011-09-09 10:36 ` George Dunlap
2011-09-09 10:46 ` Stefano Stabellini
2011-09-09 11:23 ` Keir Fraser [this message]
2011-09-09 14:13 ` Ian Campbell
2011-09-09 14:32 ` Stefano Stabellini
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=CA8FB5DF.20905%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=dunlapg@umich.edu \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 NNTP newsgroup(s).