From: Arjan van de Ven <arjan@infradead.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: virtualization@lists.osdl.org,
Ian Pratt <ian.pratt@xensource.com>,
xen-devel@lists.xensource.com, ian.pratt@cl.cam.ac.uk,
linux-kernel@vger.kernel.org,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [RFC PATCH 35/35] Add Xen virtual block device driver.
Date: Thu, 23 Mar 2006 10:42:14 +0100 [thread overview]
Message-ID: <1143106935.3147.19.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <a15cee148267ad7406a077c28c0c97ac@cl.cam.ac.uk>
> If we stick to just our own major then we break distro init scripts and
> surprise users.
btw init scripts don't really break because of this, at least sane ones
don't. It's installers that may need a few tweaks, but those are minor
at worst.
next prev parent reply other threads:[~2006-03-23 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 16:52 Ian Pratt
2006-03-22 17:09 ` Anthony Liguori
2006-03-22 23:09 ` Jeff Garzik
2006-03-24 12:17 ` Alan Cox
2006-03-24 12:38 ` Jeff Garzik
2006-03-24 13:37 ` Jeff Garzik
2006-03-24 13:40 ` Arjan van de Ven
2006-03-24 13:50 ` Jeff Garzik
2006-03-24 15:33 ` Dave C Boutcher
2006-03-24 19:04 ` Mike Christie
2006-03-24 19:19 ` Dave C Boutcher
2006-03-25 0:32 ` FUJITA Tomonori
2006-03-25 0:47 ` Roland Dreier
2006-03-24 15:55 ` Alan Cox
2006-03-25 10:03 ` Rusty Russell
2006-03-27 10:14 ` Peter Chubb
2006-03-23 8:19 ` Arjan van de Ven
2006-03-23 9:34 ` Keir Fraser
2006-03-23 9:41 ` Arjan van de Ven
2006-03-23 9:42 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 8:49 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-05-09 7:00 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-05-09 12:01 ` Christoph Hellwig
2006-03-22 6:30 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-03-22 6:31 ` [RFC PATCH 35/35] Add Xen virtual block device driver Chris Wright
2006-03-22 16:39 ` Anthony Liguori
2006-03-22 16:54 ` Christoph Hellwig
2006-03-27 8:42 ` Gerd Hoffmann
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=1143106935.3147.19.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=chrisw@sous-sol.org \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=ian.pratt@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=virtualization@lists.osdl.org \
--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
all inboxes | Powered by JetHome®