From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 4] tools: shave build yaks (part two)
Date: Thu, 31 Mar 2011 11:56:56 +0100 [thread overview]
Message-ID: <patchbomb.1301569016@localhost.localdomain> (raw)
Version 2, much of the original series has been applied. This is the
remainder.
Clean up a bunch of inconsistency, wierdness, cut-and-paste etc in the
tools/ build system. All in all it's a bit of a grab bag of stuff I
happened to notice as I was trawling
One specific useful thing which comes out of it is to isolate users of
libxl from needing to know about libxenstore or libxenctrl.
next reply other threads:[~2011-03-31 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 10:56 Ian Campbell [this message]
2011-03-31 10:56 ` [PATCH 1 of 4] tools: Remove $(CFLAGS) from links lines Ian Campbell
2011-03-31 10:56 ` [PATCH 2 of 4] libxl: do not expose libxenctrl/libxenstore headers via libxl.h Ian Campbell
2011-03-31 18:33 ` Ian Jackson
2011-04-01 13:12 ` Ian Campbell
2011-04-01 14:03 ` Ian Campbell
2011-03-31 10:56 ` [PATCH 3 of 4] tools: remove pattern matched linking rules Ian Campbell
2011-03-31 10:57 ` [PATCH 4 of 4] tools: remove some .o and binary files on clean Ian Campbell
2011-03-31 18:36 ` Ian Jackson
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=patchbomb.1301569016@localhost.localdomain \
--to=ian.campbell@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).