From: Thomas Huth <thuth@redhat.com>
To: Hanna Reitz <hreitz@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [qemu-web PATCH] Add a blog post about FUSE block exports
Date: Sun, 22 Aug 2021 15:18:52 +0200 [thread overview]
Message-ID: <541f1df5-47b4-bff7-f326-a087512c95ba@redhat.com> (raw)
In-Reply-To: <46a68d5c-cfc1-e521-8c6b-90eb74c85ede@redhat.com>
On 20/08/2021 09.56, Hanna Reitz wrote:
> On 19.08.21 18:23, Stefan Hajnoczi wrote:
>> On Thu, Aug 19, 2021 at 12:25:01PM +0200, Hanna Reitz wrote:
>>> This post explains when FUSE block exports are useful, how they work,
>>> and that it is fun to export an image file on its own path so it looks
>>> like your image file (in whatever format it was) is a raw image now.
[...]
>> This is a long blog post. One idea is to show a quickstart
>> qemu-storage-daemon FUSE export command-line in the beginning before
>> explaining all the details. That way people who just want to see what
>> this is about can get an idea without learning all the background first.
>
> Sounds good, will do. Thanks!
Oops, sorry, I just already pushed your patch to the repository since I did
not notice this conversation in time. Next time, please make sure to put
myself (and Paolo) on CC: when sending updates for qemu-web, otherwise I
might not notice the updates :-/
Thomas
next prev parent reply other threads:[~2021-08-22 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 10:25 [qemu-web PATCH] Add a blog post about FUSE block exports Hanna Reitz
2021-08-19 10:37 ` Philippe Mathieu-Daudé
2021-08-19 11:00 ` Hanna Reitz
2021-08-19 11:09 ` Philippe Mathieu-Daudé
2021-08-19 11:17 ` Hanna Reitz
2021-08-19 16:23 ` Stefan Hajnoczi
2021-08-20 7:56 ` Hanna Reitz
2021-08-20 9:21 ` Daniel P. Berrangé
2021-08-20 14:27 ` Stefan Hajnoczi
2021-08-22 13:18 ` Thomas Huth [this message]
2021-08-23 8:30 ` Hanna Reitz
2021-08-23 8:49 ` Thomas Huth
2021-08-19 18:22 ` Klaus Kiwi
2021-08-20 9:03 ` Hanna Reitz
2021-08-20 21:24 ` Eric Blake
2021-08-23 8:23 ` Hanna Reitz
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=541f1df5-47b4-bff7-f326-a087512c95ba@redhat.com \
--to=thuth@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.