qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, afrosi@redhat.com, qemu-devel@nongnu.org,
	mreitz@redhat.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [qemu-web PATCH] Add QEMU storage overview blog post
Date: Mon, 14 Sep 2020 12:53:52 +0200	[thread overview]
Message-ID: <226a454f-3d8d-749b-ca25-b3f3f1912d0b@redhat.com> (raw)
In-Reply-To: <20200914103507.GG579094@stefanha-x1.localdomain>

On 14/09/2020 12.35, Stefan Hajnoczi wrote:
> On Mon, Sep 07, 2020 at 04:04:21PM +0100, Stefan Hajnoczi wrote:
>> I want to kick of a series of posts about storage. The first post covers
>> high-level concepts, features, and utilities in QEMU. Later posts will
>> discuss configuration details, architecture, and performance.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>>  _posts/2020-09-07-qemu-storage-overview.md | 122 +++++++
>>  screenshots/2020-09-07-block-device-io.svg | 366 +++++++++++++++++++++
>>  screenshots/2020-09-07-lifecycle.svg       | 328 ++++++++++++++++++
>>  3 files changed, 816 insertions(+)
>>  create mode 100644 _posts/2020-09-07-qemu-storage-overview.md
>>  create mode 100644 screenshots/2020-09-07-block-device-io.svg
>>  create mode 100644 screenshots/2020-09-07-lifecycle.svg
> 
> Ping? Thomas, you would you be able to merge this?

Sorry, your mail successfully hid in my overcrowded inbox :-( ... thanks
to Paolo for pushing it!

 Thomas



      parent reply	other threads:[~2020-09-14 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07 15:04 [qemu-web PATCH] Add QEMU storage overview blog post Stefan Hajnoczi
2020-09-14 10:35 ` Stefan Hajnoczi
2020-09-14 10:46   ` Paolo Bonzini
2020-09-14 10:53   ` Thomas Huth [this message]

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=226a454f-3d8d-749b-ca25-b3f3f1912d0b@redhat.com \
    --to=thuth@redhat.com \
    --cc=afrosi@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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 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).