From: Don Slutz <dslutz@verizon.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
stefano.stabellini@eu.citrix.com, Jan Beulich <JBeulich@suse.com>,
Don Slutz <dslutz@verizon.com>,
ian.campbell@citrix.com
Subject: Re: [PATCH] Allow building of XEN from source on a system without internet access.
Date: Tue, 15 Oct 2013 11:39:05 -0400 [thread overview]
Message-ID: <525D6199.2080105@terremark.com> (raw)
In-Reply-To: <21084.4915.234656.280009@mariner.uk.xensource.com>
On 10/14/13 11:52, Ian Jackson wrote:
> Don Slutz writes ("Re: [Xen-devel] [PATCH] Allow building of XEN from source on a system without internet access."):
>> On 10/04/13 09:24, Jan Beulich wrote:
> ...
>>>> -XEN_EXTFILES_URL=http://xenbits.xen.org/xen-extfiles
>>>> +XEN_EXTFILES_URL ?= http://xenbits.xen.org/xen-extfiles
>>> Given the change here and further down - what is it that doesn't
>>> work when you run "make XEN_EXTFILES_URL=..."? I understand
>>> that you may want to pass these settings through the environment,
>>> but if the command line approach works the patch title is wrong.
>> Yes, these are passed via the environment. Will fix the patch title.
> Right, thanks.
>
> FAOD I approve of this kind of change, but did you know that you can
> put settings like this in .config in the root of the Xen tree ?
I did. So how about a title of "Allow building of XEN from source on a
system without internet access by specifying external stuff in .config"?
-Don Slutz
> Ian.
next prev parent reply other threads:[~2013-10-15 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 13:17 [PATCH] Allow building of XEN from source on a system without internet access Don Slutz
2013-10-04 13:24 ` Jan Beulich
2013-10-04 18:43 ` Don Slutz
2013-10-14 15:52 ` Ian Jackson
2013-10-15 15:39 ` Don Slutz [this message]
2013-10-31 19:04 ` Ian Campbell
2013-11-05 2:01 ` Don Slutz
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=525D6199.2080105@terremark.com \
--to=dslutz@verizon.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.