From: Daniel Kiper <daniel.kiper@oracle.com>
To: ian.jackson@eu.citrix.com, jbeulich@suse.com,
stefano.stabellini@eu.citrix.com, xen-devel@lists.xensource.com
Subject: [PATCH 0/3] Build system fixes for Xen 4.1.6
Date: Wed, 24 Jul 2013 16:06:36 +0200 [thread overview]
Message-ID: <1374674799-16465-1-git-send-email-daniel.kiper@oracle.com> (raw)
Hi,
As Ian Jackson asked I am sending build system fixes based
on patches applied a few weeks ago to Xen unstable. Earlier
patches which did not required any changes were applied to
Xen 4.1.6. This patch series contains only applicable patches
which must be modified to be applied.
List of patches:
- stubdom: Clean extras/mini-os directory during make clean,
- stubdom: Do not create dangling links,
- Silently ignore include errors during make distclean.
Daniel
next reply other threads:[~2013-07-24 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:06 Daniel Kiper [this message]
2013-07-24 14:06 ` [PATCH 1/3] stubdom: Clean extras/mini-os directory during make clean Daniel Kiper
2013-07-24 14:06 ` [PATCH 2/3] stubdom: Do not create dangling links Daniel Kiper
2013-07-24 14:06 ` [PATCH 3/3] Silently ignore include errors during make distclean Daniel Kiper
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=1374674799-16465-1-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--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).