From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] qcow2: Add metadata overlap checks
Date: Mon, 26 Aug 2013 16:23:19 +0200 [thread overview]
Message-ID: <521B64D7.7050303@redhat.com> (raw)
In-Reply-To: <1377512306-27382-1-git-send-email-mreitz@redhat.com>
Hi,
Okay, so this did arrive after all (albeit 4 h late) – sorry for the
duplicate (see the series from 15:18).
Kind regards,
Max
next prev parent reply other threads:[~2013-08-26 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 10:18 [Qemu-devel] [PATCH 0/5] qcow2: Add metadata overlap checks Max Reitz
2013-08-26 10:18 ` [Qemu-devel] [PATCH 1/5] qcow2: Add corrupt bit Max Reitz
2013-08-26 10:18 ` [Qemu-devel] [PATCH 2/5] qcow2: Metadata overlap checks Max Reitz
2013-08-26 10:18 ` [Qemu-devel] [PATCH 3/5] qcow2: Employ metadata " Max Reitz
2013-08-26 10:18 ` [Qemu-devel] [PATCH 4/5] qcow2: Check allocations in qcow2_check Max Reitz
2013-08-26 10:18 ` [Qemu-devel] [PATCH 5/5] qemu-iotests: Overlapping cluster allocations Max Reitz
2013-08-26 14:23 ` Max Reitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-26 13:04 [Qemu-devel] [PATCH 0/5] qcow2: Add metadata overlap checks Max 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=521B64D7.7050303@redhat.com \
--to=mreitz@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).