qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Reitz <hreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Klaus Kiwi <kkiwi@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [qemu-web PATCH] Update FUSE block export blog post
Date: Tue, 7 Sep 2021 17:54:36 +0200	[thread overview]
Message-ID: <c01c99d6-4c31-cbf1-cc5b-37d79f981cc1@redhat.com> (raw)
In-Reply-To: <8abf1571-cef6-e3ee-b2ce-1528801b4b17@redhat.com>

On 07.09.21 16:07, Thomas Huth wrote:
> On 06/09/2021 18.29, Hanna Reitz wrote:
>> Because I forgot to CC Thomas on the discussion adding this post, it was
>> merged prematurely.  This patch updates the post to incorporate the
>> feedback I received on it:
>>
>> - Title change: This article mostly deals with presenting a guest image
>>    in one image format as a raw image, so the title should reflect that;
>>    there is much less focus on exporting block devices from a live VM
>>
>> - Mention libguestfs, and contrast against it; make a note that
>>    libguestfs provides security that FUSE exports cannot provide
>>
>> - Have a full example in the intro, to show where we are going with this
>>    post
>>
>> - Some heading depths changed (nesting did not really make sense)
>>
>> - Be more explicit that by "file mounts" I do not mean a filesystem with
>>    a root directory and a single file in it
>>
>> - Explicitly mention that "/" is a directory without a name, to
>>    illustrate the fact that root nodes do not have names
>>
>> - Short intro for "QEMU block exports", explaining its place in this
>>    post
>>
>> - Make all exports writable
>>
>> - Use "exp0" as export ID to get shorter lines that fit better into 80
>>    characters
>>
>> - Reference the intro example in the intro of "Mounting an image on
>>    itself"
>>
>> - Show "qemu-fuse-disk-export.py" in *italic* instead of as `code`
>>    (because I had all other command names in *italic*)
>>
>> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
>> ---
>>   _posts/2021-08-22-fuse-blkexport.md | 145 ++++++++++++++++++++++------
>>   1 file changed, 117 insertions(+), 28 deletions(-)
>
> Thanks, changes looked fine to me, so I've pushed it now.

Thanks!

Hanna



  reply	other threads:[~2021-09-07 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 16:29 [qemu-web PATCH] Update FUSE block export blog post Hanna Reitz
2021-09-07 14:07 ` Thomas Huth
2021-09-07 15:54   ` Hanna Reitz [this message]
2021-09-07 17:52 ` Eric Blake
2021-09-14 10:02   ` 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=c01c99d6-4c31-cbf1-cc5b-37d79f981cc1@redhat.com \
    --to=hreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kkiwi@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@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 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).