From: Fam Zheng <famcool@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] qemu-iotests: Filter out "qemu-io> " in all tests
Date: Fri, 29 Nov 2013 08:36:21 +0800 [thread overview]
Message-ID: <5297E185.9000000@gmail.com> (raw)
In-Reply-To: <52978416.4000606@redhat.com>
于2013年11月29日 星期五 01时57分42秒,Eric Blake写到:
> On 11/28/2013 07:49 AM, Kevin Wolf wrote:
>
>>>>>> https://github.com/famz/qemu.git 035-filter-qemu-io
>>>>>>
>>>>>> v2: Rebase to current master.
>>>>>> [01] Add Reviewed-by for Eric.
>>>>>> [02] Update comment to describe the command for mechanical substitution. (Eric)
>>>>>
>>>>> Kevin, would you like to take this one?
>>>>
>>>> I would, but this way it simply doesn't work.
>>>>
>>>> The '035-filter-qemu-io' branch in your repo is something, but certainly
>>>> not this series. It may be some early RFC where you only fixed one case.
>>>> I then found the 'iotests-filter-qemu-io' (which is already not what you
>>>> said) branch and I almost would have applied it, but I noticed it's not
>>>> exactly the same as this series; I suppose it's version 1.
>>>>
>>>> Eric reviewed _something_, but the two branches I found aren't what you
>>>> sent, and he didn't specify the commit ID he reviewed, so I can't put
>>>> his Reviewed-by tag anywhere, because I simply don't know what he looked
>>>> at.
>
> And I've since lost track of which commit id I reviewed.
>
>>>>
>>>> Fam, can you push the _current_ version somewhere and tell me the
>>>> correct branch name and commit ID? Eric, can you then tell me if this
>>>> newly pushed code matches what you reviewed?
>>>
>>> Sorry, I've pushed again to:
>>>
>>> https://github.com/famz/qemu.git for-kevin
>>>
>>> Please fetch again.
>>
>> Thanks, cherry-picked the patches from that branch (commit ID of the
>> top is 0974950e05137c7751ec1d3c5d1b0fa5387eead9). I didn't add Eric's
>> Reviewed-by yet, but I'll do so when he confirms that this is what he
>> checked.
>
> I have now reviewed commit 0974950e05137c7751ec1d3c5d1b0fa5387eead9 in
> the same manner as before (manually followed the 'sed' instructions in
> the commit message and verified that the only differences remaining are
> the added filter). It appears that the only differences in this known
> commit id from whatever (now unknown) commit I first reviewed is thus
> limited to rebase differences. I'm happy with the commit, so feel free
> to (re-)add:
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
Thanks Eric. I'm sorry for the trouble.
Fam
next prev parent reply other threads:[~2013-11-29 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 2:25 [Qemu-devel] [PATCH v2 0/2] qemu-iotests: Filter out "qemu-io> " in all tests Fam Zheng
2013-11-20 2:25 ` [Qemu-devel] [PATCH v2 1/2] qemu-iotests: Filter qemu-io output in 025 Fam Zheng
2013-11-20 2:25 ` [Qemu-devel] [PATCH v2 2/2] qemu-iotests: Filter out 'qemu-io> ' prompt Fam Zheng
2013-11-20 2:35 ` Eric Blake
2013-11-27 2:01 ` [Qemu-devel] [PATCH v2 0/2] qemu-iotests: Filter out "qemu-io> " in all tests Fam Zheng
2013-11-28 11:56 ` Kevin Wolf
2013-11-28 14:34 ` Fam Zheng
2013-11-28 14:49 ` Kevin Wolf
2013-11-28 17:57 ` Eric Blake
2013-11-29 0:36 ` Fam Zheng [this message]
2013-11-29 9:37 ` Kevin Wolf
2013-11-28 14:39 ` Fam Zheng
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=5297E185.9000000@gmail.com \
--to=famcool@gmail.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).