From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: 陳培泓 <pahome.chen@mirlab.org>, "QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Can I mount encrypt qcow2?
Date: Fri, 21 Jul 2017 15:06:31 +0100 [thread overview]
Message-ID: <20170721140631.GS17693@redhat.com> (raw)
In-Reply-To: <18c3027a-d30b-98df-9693-826751f80ea9@redhat.com>
On Fri, Jul 21, 2017 at 09:05:21AM -0500, Eric Blake wrote:
> On 07/21/2017 07:18 AM, Eric Blake wrote:
> > [please don't top-post on technical lists]
> >
> > On 07/21/2017 04:41 AM, 陳培泓 wrote:
> >> oh Maybe the version is something wrong?
> >>
> >> qemu-img -V
> >>
> >>> qemu-img version 2.9.0
> >>
> >>
> >> qemu-nbd -V
> >>
> >>> qemu-nbd version 0.0.1
> >>
> >>
> >> They're not correspondent?
> >
> > Not currently, although patches are welcome (qemu-img and qemu-io share
> > versions, so qemu-nbd is the only oddball)
>
> Oops, looks like 'git send-email' doesn't know how to auto-cc
> 'Reported-by:' tags.
That's something that's bugged me too - someone should write a patch for
git :-)
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-21 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 2:43 [Qemu-devel] Can I mount encrypt qcow2? 陳培泓
2017-07-20 8:59 ` Daniel P. Berrange
2017-07-20 9:07 ` 陳培泓
2017-07-20 9:12 ` Daniel P. Berrange
2017-07-21 1:44 ` 陳培泓
2017-07-21 8:38 ` Daniel P. Berrange
2017-07-21 9:31 ` 陳培泓
2017-07-21 9:34 ` Daniel P. Berrange
2017-07-21 9:41 ` 陳培泓
2017-07-21 12:18 ` Eric Blake
2017-07-21 14:05 ` Eric Blake
2017-07-21 14:06 ` Daniel P. Berrange [this message]
2017-07-21 14:18 ` Eric Blake
2017-07-24 1:49 ` 陳培泓
2017-07-24 12:25 ` Eric Blake
2017-07-25 4:26 ` lampahome
2017-07-25 11:26 ` Eric Blake
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=20170721140631.GS17693@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pahome.chen@mirlab.org \
--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 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.