From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] Add tar container format
Date: Thu, 13 Aug 2009 18:15:33 -0500 [thread overview]
Message-ID: <4A849E95.2090200@codemonkey.ws> (raw)
In-Reply-To: <4A849E17.3030901@codemonkey.ws>
Anthony Liguori wrote:
> If others agree, I think we should start going down this road.
> block-tar/block-dictzip seem like obvious candidates for plugins.
And at some point in the distant future, I think it would also make
sense for the block layer, once librarized and such, to be split out
into a separate sub-project.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-13 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 15:33 [Qemu-devel] [PATCH] Add tar container format Alexander Graf
2009-08-13 22:57 ` Anthony Liguori
2009-08-13 23:08 ` Alexander Graf
2009-08-13 23:13 ` Anthony Liguori
2009-08-13 23:15 ` Anthony Liguori [this message]
2009-08-15 20:36 ` Christoph Hellwig
2009-08-17 12:05 ` [Qemu-devel] " Paolo Bonzini
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=4A849E95.2090200@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--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).