From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH for-4.7] travis: drop broken LLVM repos
Date: Tue, 7 Jun 2016 17:17:26 +0100 [thread overview]
Message-ID: <22358.62358.862847.544846@mariner.uk.xensource.com> (raw)
In-Reply-To: <1465315732-48921-1-git-send-email-cardoe@cardoe.com>
Doug Goldstein writes ("[PATCH for-4.7] travis: drop broken LLVM repos"):
> LLVM repos are currently down so drop them from being installed so we
> can get some testing back.
This is unfortunate churn to be having in our tree. I'm happy for
this removal commit to go in, but isn't there a way to deal with this
that doesn't involve updating a metadata file in xen.git ?
(This kind of external repo dependency is one reason why osstest likes
to fetch its inputs from a very small number of different places, with
many files and trees copied to xenbits.)
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-07 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:08 [PATCH for-4.7] travis: drop broken LLVM repos Doug Goldstein
2016-06-07 16:17 ` Ian Jackson [this message]
2016-06-07 17:07 ` Doug Goldstein
2016-06-07 16:20 ` Wei Liu
2016-06-07 17:09 ` Doug Goldstein
2016-06-07 17:34 ` Wei Liu
2016-06-08 9:28 ` Jan Beulich
2016-06-08 10:09 ` Dario Faggioli
2016-06-08 11:44 ` Wei Liu
2016-06-08 11:59 ` Jan Beulich
2016-06-08 12:28 ` Doug Goldstein
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=22358.62358.862847.544846@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=jbeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).