From: Don Slutz <dslutz@verizon.com>
To: xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Don Slutz <dslutz@verizon.com>
Subject: [PATCH v2 0/1] Allow building of XEN from source on a system without internet access.
Date: Mon, 4 Nov 2013 20:56:22 -0500 [thread overview]
Message-ID: <1383616583-1945-1-git-send-email-dslutz@terremark.com> (raw)
From: Don Slutz <dslutz@verizon.com>
Changes v1 to v2:
Reword the commit message to be clearer.
Don Slutz (1):
.config: Allow all URL(s) to be specified in .config
Config.mk | 6 +++---
tools/firmware/etherboot/Makefile | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
--
1.8.4
next reply other threads:[~2013-11-05 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 1:56 Don Slutz [this message]
2013-11-05 1:56 ` [PATCH v2 1/1] .config: Allow all URL(s) to be specified in .config Don Slutz
2013-11-05 13:48 ` Ian Campbell
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=1383616583-1945-1-git-send-email-dslutz@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.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).