From: Peter Lieven <pl@kamp.de>
To: "Liguori, Anthony" <aliguori@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] qemu-img convert cache mode for source
Date: Thu, 06 Mar 2014 19:07:15 +0100 [thread overview]
Message-ID: <5318B953.1010303@kamp.de> (raw)
In-Reply-To: <D813B0A2A0FFE24B98990E82EC900AF1417475@ex10-mbx-36008.ant.amazon.com>
Hi Anthony,
Am 06.03.2014 15:19, schrieb Liguori, Anthony:
> We can check the moderation queue although it's usually empty. Savannah has a pretty aggressive spam filter and mail delivery isn't always reliable.
It would be good to know why these mails got lost. It seems to have happened sometimes in the past as well.
Thanks,
Peter
>
> Regards,
>
> Anthony Liguori
>
> ________________________________________
> From: Paolo Bonzini [paolo.bonzini@gmail.com] on behalf of Paolo Bonzini [pbonzini@redhat.com]
> Sent: Thursday, March 06, 2014 3:29 AM
> To: Stefan Hajnoczi; Peter Lieven
> Cc: Kevin Wolf; qemu-devel@nongnu.org; Stefan Hajnoczi; Liguori, Anthony
> Subject: Re: qemu-img convert cache mode for source
>
> Il 06/03/2014 11:29, Stefan Hajnoczi ha scritto:
>> On Wed, Mar 05, 2014 at 03:44:17PM +0100, Peter Lieven wrote:
>>> [PATCH] block: introduce BDRV_O_SEQUENTIAL
>> It hasn't shown up on the mailing list yet.
>>
>> I received it privately because I am CCed but it needs to be on the list
>> in order to get review and be merged.
>>
>> Anthony: how can Peter troubleshoot a patch email that isn't appearing
>> on the mailing list?
> Maybe it's been caught by the savannah spam filter.
>
> Paolo
>
next prev parent reply other threads:[~2014-03-06 18:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 10:14 [Qemu-devel] qemu-img convert cache mode for source Peter Lieven
2014-02-26 15:41 ` Stefan Hajnoczi
2014-02-26 15:54 ` Eric Blake
2014-02-26 16:01 ` Peter Lieven
2014-02-27 8:57 ` Stefan Hajnoczi
2014-02-28 14:35 ` Peter Lieven
2014-03-03 10:38 ` Kevin Wolf
2014-03-03 11:20 ` Peter Lieven
2014-03-03 12:59 ` Paolo Bonzini
2014-03-03 13:07 ` Peter Lieven
2014-03-03 12:03 ` Stefan Hajnoczi
2014-03-03 12:20 ` Peter Lieven
2014-03-04 9:24 ` Stefan Hajnoczi
2014-03-05 14:44 ` Peter Lieven
2014-03-05 15:20 ` Marcus
2014-03-05 15:53 ` Peter Lieven
2014-03-05 17:38 ` Marcus
2014-03-05 18:09 ` Peter Lieven
2014-03-06 10:41 ` Stefan Hajnoczi
2014-03-06 18:58 ` Peter Lieven
2014-03-06 10:29 ` Stefan Hajnoczi
2014-03-06 11:29 ` Paolo Bonzini
2014-03-06 14:19 ` Liguori, Anthony
2014-03-06 18:07 ` Peter Lieven [this message]
2014-03-07 8:03 ` Peter Lieven
2014-02-27 1:10 ` Fam Zheng
2014-02-27 11:07 ` Kevin Wolf
2014-02-27 16:12 ` Peter Lieven
2014-03-03 10:40 ` Kevin Wolf
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=5318B953.1010303@kamp.de \
--to=pl@kamp.de \
--cc=aliguori@amazon.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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).