From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff
Date: Wed, 31 Jul 2013 16:35:27 +0100 [thread overview]
Message-ID: <1375284927.7382.107.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <51F92D63.2000802@citrix.com>
On Wed, 2013-07-31 at 16:29 +0100, Andrew Cooper wrote:
> On 31/07/13 16:15, Ian Campbell wrote:
> > depends on "autoconf: regenerate configure scripts with 4.4 version"
> >
> > This series removes some of the really old deadwood from the tools build
> > and makes some other things which are on their way out configurable at
> > build time with a default depending on how far down the slope I judge
> > them to be.
> >
> > * nuke in tree copy of libaio
> > * nuke obsolete tools: xsview, miniterm, lomount & sv
> > * make xend optional, still on by default (for now!)
> > * disable blktap1 by default (needs qemu patch, just posted)
> > * some cleanup of .*ignore
> >
> > Ian.
>
> In what way is lomount obsolete? XenServer relies on it and I am
> unaware of any alternative.
As referenced in the actual patch: kpartx
> Other than that, I am very happy about the other nuked items which
> allows me to clean up some of our local hacks to the upstream build system.
>
> ~Andrew
>
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-07-31 15:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 15:15 [PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff Ian Campbell
2013-07-31 15:15 ` [PATCH 1/9] tools: move xm and xend under tools python Ian Campbell
2013-08-07 15:03 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 2/9] tools: make building xend configurable Ian Campbell
2013-08-07 15:04 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 3/9] tools: remove in tree libaio Ian Campbell
2013-08-01 8:38 ` Egger, Christoph
2013-08-01 14:39 ` Ian Campbell
2013-08-07 15:06 ` Ian Jackson
2013-08-08 9:07 ` Ian Campbell
2013-08-20 14:28 ` Ian Campbell
2013-07-31 15:15 ` [PATCH 4/9] tools: delete xsview Ian Campbell
2013-08-07 15:06 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 5/9] tools: remove miniterm Ian Campbell
2013-08-07 15:07 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 6/9] tools: remove lomount Ian Campbell
2013-08-07 15:08 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 7/9] .*ignore: remove some cruft Ian Campbell
2013-08-07 15:09 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 8/9] tools: disable blktap1 build by default Ian Campbell
2013-08-07 15:13 ` Ian Jackson
2013-07-31 15:15 ` [PATCH 9/9] tools: drop 'sv' Ian Campbell
2013-08-07 15:13 ` Ian Jackson
2013-07-31 15:29 ` [PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff Andrew Cooper
2013-07-31 15:35 ` Ian Campbell [this message]
2013-07-31 15:57 ` Andrew Cooper
2013-07-31 16:37 ` Andrew Cooper
2013-08-01 6:11 ` Matt Wilson
2013-08-20 15:03 ` Ian Campbell
2013-08-12 14:53 ` Fabio Fantoni
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=1375284927.7382.107.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--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).