All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Naphtali Sprei <nsprei@redhat.com>
Cc: Sheng Yang <sheng@linux.intel.com>, Kevin Wolf <kwolf@redhat.com>,
	kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Fix qemu-img can't create qcow image based on read-only image
Date: Thu, 11 Feb 2010 11:24:42 -0600	[thread overview]
Message-ID: <4B743D5A.7080906@codemonkey.ws> (raw)
In-Reply-To: <4B743CAB.4050508@redhat.com>

On 02/11/2010 11:21 AM, Naphtali Sprei wrote:
> Anthony Liguori wrote:
>    
>> On 01/28/2010 08:15 PM, Sheng Yang wrote:
>>      
>>> Commit 03cbdac7 "Disable fall-back to read-only when cannot open drive's
>>> file for read-write" result in read-only image can't be used as backed
>>> image in qemu-img.
>>>
>>> Cc: Naphtali Sprei<nsprei@redhat.com>
>>> Signed-off-by: Sheng Yang<sheng@linux.intel.com>
>>>
>>>        
>> Applied.  Thanks.
>>      
> I've sent a patch that includes this patch, too ( http://lists.gnu.org/archive/html/qemu-devel/2010-02/msg00578.html )
> Should I rebase my patch ?
>    

Yes.

Regards,

Anthony Liguori

>    Naphtali
>
>
>    
>> Regards,
>>
>> Anthony Liguori
>>      
>
>    


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Naphtali Sprei <nsprei@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Sheng Yang <sheng@linux.intel.com>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-img: Fix qemu-img can't create qcow image based on read-only image
Date: Thu, 11 Feb 2010 11:24:42 -0600	[thread overview]
Message-ID: <4B743D5A.7080906@codemonkey.ws> (raw)
In-Reply-To: <4B743CAB.4050508@redhat.com>

On 02/11/2010 11:21 AM, Naphtali Sprei wrote:
> Anthony Liguori wrote:
>    
>> On 01/28/2010 08:15 PM, Sheng Yang wrote:
>>      
>>> Commit 03cbdac7 "Disable fall-back to read-only when cannot open drive's
>>> file for read-write" result in read-only image can't be used as backed
>>> image in qemu-img.
>>>
>>> Cc: Naphtali Sprei<nsprei@redhat.com>
>>> Signed-off-by: Sheng Yang<sheng@linux.intel.com>
>>>
>>>        
>> Applied.  Thanks.
>>      
> I've sent a patch that includes this patch, too ( http://lists.gnu.org/archive/html/qemu-devel/2010-02/msg00578.html )
> Should I rebase my patch ?
>    

Yes.

Regards,

Anthony Liguori

>    Naphtali
>
>
>    
>> Regards,
>>
>> Anthony Liguori
>>      
>
>    

  reply	other threads:[~2010-02-11 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29  2:15 [PATCH v2] qemu-img: Fix qemu-img can't create qcow image based on read-only image Sheng Yang
2010-01-29  2:15 ` [Qemu-devel] " Sheng Yang
2010-01-29  7:23 ` Kevin Wolf
2010-01-29  7:23   ` Kevin Wolf
2010-01-31 10:24 ` Naphtali Sprei
2010-01-31 10:24   ` [Qemu-devel] " Naphtali Sprei
2010-02-10 18:31 ` [Qemu-devel] " Anthony Liguori
2010-02-10 18:31   ` Anthony Liguori
2010-02-11 17:21   ` Naphtali Sprei
2010-02-11 17:21     ` Naphtali Sprei
2010-02-11 17:24     ` Anthony Liguori [this message]
2010-02-11 17:24       ` Anthony Liguori

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=4B743D5A.7080906@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=nsprei@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sheng@linux.intel.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.