From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Allow 'qemu-img convert' to preserve the backing file
Date: Wed, 28 May 2008 12:58:23 +0100 [thread overview]
Message-ID: <20080528115823.GB19738@shareable.org> (raw)
In-Reply-To: <18493.11141.847907.619324@mariner.uk.xensource.com>
Ian Jackson wrote:
> So definitely something to discuss with upstream.
Is qemu-devel not the most upstream place for qemu development?
(By the way, vpc format is broken in qemu-img. Should I not be
reporting it on qemu-devel then, but somewhere else?)
-- Jamie
next prev parent reply other threads:[~2008-05-28 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 5:02 [Qemu-devel] [RFC] Allow 'qemu-img convert' to preserve the backing file Marc Bevand
2008-05-28 9:53 ` Ian Jackson
2008-05-28 9:55 ` Ian Jackson
2008-05-30 8:43 ` [Qemu-devel] " Marc Bevand
2008-05-30 9:21 ` [Qemu-devel] [PATCH] New qemu-img convert -B option to preserve the COW aspect of images and/or re-base them Marc Bevand
2008-05-28 11:58 ` Jamie Lokier [this message]
2008-05-28 13:22 ` [Qemu-devel] [RFC] Allow 'qemu-img convert' to preserve the backing file 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=20080528115823.GB19738@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.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).