qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 1/5] cpus: correct coding style in qmp_memsav


From: Simon Ruderich
Subject: Re: [Qemu-devel] [PATCH v2 1/5] cpus: correct coding style in qmp_memsave/qmp_pmemsave
Date: Sun, 22 Apr 2018 11:19:14 +0200
User-agent: Mutt/1.9.5 (2018-04-13)

On Tue, Apr 17, 2018 at 03:56:58PM -0500, Eric Blake wrote:
> On 04/12/2018 07:50 AM, Simon Ruderich wrote:
>> Signed-off-by: Simon Ruderich <address@hidden>
>> ---
>>  cpus.c | 6 ++++--
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> Reviewed-by: Eric Blake <address@hidden>
>
> However, as a meta-comment, this message was sent with:
>
>> Message-Id: <address@hidden>
>> In-Reply-To: <address@hidden>
>> References: <address@hidden>
>
> Looking on patchew, I see:
> http://patchew.org/QEMU/address@hidden/
> The requested URL /QEMU/address@hidden/ was not
> found on this server.
>
> For most messages, looking up the In-Reply-To: message-id gives the
> cover letter (for example,
> http://patchew.org/QEMU/address@hidden/)
>
> Similarly, looking on the list archives, I don't see the 0/5 cover
> letter, but rather that your messages are treated as threaded to your v1
> thread:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-04/threads.html#01388
>
> For the sake of tooling, it's best to send a v2 series with a new cover
> letter as a new top-level thread.

Yeah, I screwed that part up. Sorry for the extra work. Will fix
when I resend the series.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9



reply via email to

[Prev in Thread] Current Thread [Next in Thread]