qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jun Li <junmuzi@gmail.com>
To: Fam Zheng <famz@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, Jun Li <juli@redhat.com>,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] snapshot: fixed bdrv_get_full_backing_filename can not get correct full_backing_filename
Date: Sat, 17 May 2014 20:37:30 +0800	[thread overview]
Message-ID: <5377580A.5060209@gmail.com> (raw)
In-Reply-To: <20140514130538.GA19672@T430.nay.redhat.com>


On 05/14/2014 09:05 PM, Fam Zheng wrote:
> On Wed, 05/14 14:40, Stefan Hajnoczi wrote:
>> On Sun, May 11, 2014 at 12:35:57AM +0800, Jun Li wrote:
>>> From: Jun Li <junmuzi@gmail.com>
>>>
>>> This patch fixed the following bug:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1084302 .
>>>
>>> path_combine can not calculate the correct full path name for backing_file.
>>> Such as:
>>> create a snapshot chain:
>>> sn2->sn1->$BASE_IMG
>>> backing file is : /home/wookpecker/img.qcow2
>>> sn1 : /home/woodpecker/tmp/sn1
>>> sn2 : /home/woodpecker/tmp/sn2
>>> when create sn2, path_combine can not got a correct path for $BASE_IMG.
>>>
>>> In this patch, will check the backing_filename is a symlink or not firstly,
>>> then return the full(absolute) path via realpath.
>>>
>>> Signed-off-by: Jun Li <junmuzi@gmail.com>
>>> ---
>>>   block.c | 18 +++++++++++++++++-
>>>   1 file changed, 17 insertions(+), 1 deletion(-)
>> Please fix your patch email submission process so it doesn't send the
>> same patch multiple times.
ok , thx.
>> You've done this several times in the past.  It makes patch review more
>> difficult than it needs to be for reviewers.  If I have to compare
>> several emails and figure out which patch is the right one before
>> reviewing I'm inclined not to review at all.
ok, thank you very much.
>>
> This is indeed very confusing. (I've showed Jun the configuration I have to
> send patches.)
>
> If you hit enter too quickly or forgot something, it's OK to try again, but
> using distinct subjects is important and makes it easier for us to know what's
> happening.
>
> If, by mistake the subjects you send are the same, please reply yourself to the
> list, saying "please ignore this one", so we know which to look at.
ok, got it. Thx.
>
> Fam
Thanks Fam and Stefan, I have configured my msmtp(via gmail) 
successfully. As I specify the wrong smtpserver with smtp.gmail.com 
before, now the gmail smtpserver is smtp.googlemail.com.

Best Regards,
Jun Li

  reply	other threads:[~2014-05-17 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 16:35 [Qemu-devel] [PATCH v3] snapshot: fixed bdrv_get_full_backing_filename can not get correct full_backing_filename Jun Li
2014-05-12 15:15 ` Eric Blake
2014-05-18 10:34   ` Jun Li
2014-05-25 13:37     ` Jun Li
2014-05-25 13:35   ` Jun Li
2014-05-14 12:40 ` Stefan Hajnoczi
2014-05-14 13:05   ` Fam Zheng
2014-05-17 12:37     ` Jun Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-10 16:32 Jun Li
2014-05-10 16:30 Jun Li

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=5377580A.5060209@gmail.com \
    --to=junmuzi@gmail.com \
    --cc=famz@redhat.com \
    --cc=juli@redhat.com \
    --cc=kwolf@redhat.com \
    --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).