All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	ian.jackson@eu.citrix.com, Jan Beulich <JBeulich@suse.com>,
	Don Slutz <dslutz@verizon.com>,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] Allow building of XEN from source on a system without internet access.
Date: Mon, 4 Nov 2013 21:01:00 -0500	[thread overview]
Message-ID: <5278515C.2020706@terremark.com> (raw)
In-Reply-To: <1383246252.5436.87.camel@dagon.hellion.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 546 bytes --]

On 10/31/13 15:04, Ian Campbell wrote:
> On Fri, 2013-10-04 at 14:43 -0400, Don Slutz wrote:
>
>> Yes, these are passed via the environment.  Will fix the patch title.
> I don't think I saw this, did I miss it or is it still pending?
>
>
Sorry about the slow response.

It was still pending (v2 is out).  I was not happy with the title:

    Allow building of XEN from source on a system without internet
    access by specifying external stuff in .config


I think the newer one is better.  Also I spent time on kexec stuff 1st.
     -Don Slutz

[-- Attachment #1.2: Type: text/html, Size: 1136 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2013-11-05  2:01 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
2013-10-31 19:04     ` Ian Campbell
2013-11-05  2:01       ` Don Slutz [this message]

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=5278515C.2020706@terremark.com \
    --to=dslutz@verizon.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.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.