From: harry@hebutterworth.freeserve.co.uk
To: Rusty Russell <rusty@rustcorp.com.au>,
Anthony Liguori <aliguori@us.ibm.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
Jeremy Katz <katzj@redhat.com>,
Xen Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: Re: Proposal for init/kexec/hotplug format for Xen
Date: Mon, 28 Feb 2005 13:22:42 +0100 (CET) [thread overview]
Message-ID: <1463693.1109593362044.JavaMail.www@wwinf3101> (raw)
Why have two separate mechanisms when the mechanism required for hotplug can be used to build the tree from scratch?
--
Whatever you Wanadoo:
http://www.wanadoo.co.uk/time/
This email has been checked for most known viruses - find out more at: http://www.wanadoo.co.uk/help/id/7098.htm
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-28 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 12:22 harry [this message]
2005-02-28 13:02 ` Re: Proposal for init/kexec/hotplug format for Xen Rusty Russell
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=1463693.1109593362044.JavaMail.www@wwinf3101 \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=aliguori@us.ibm.com \
--cc=katzj@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=xen-devel@lists.sourceforge.net \
/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.