qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, Cornelia Huck <cohuck@redhat.com>
Cc: pasic@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
	richard.henderson@linaro.org, qemu-devel@nongnu.org,
	agraf@suse.de, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH 0/4] four zpci patches
Date: Mon, 28 Aug 2017 11:26:07 +0800	[thread overview]
Message-ID: <d47733fa-6f24-1bba-a54f-373a9074c9fd@linux.vnet.ibm.com> (raw)
In-Reply-To: <20d23300-2f98-7b38-afab-4c8971afb356@redhat.com>



在 2017/8/25 上午12:27, Eric Blake 写道:
> On 08/24/2017 03:48 AM, Yi Min Zhao wrote:
>>
>> 在 2017/8/24 下午3:13, Cornelia Huck 写道:
>>> On Thu, 24 Aug 2017 13:20:12 +0800
>>> Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
>>>
>>>> Why can't I receive [Qemu-devel] prefixed patches?
>> I sent patches to qemu-devel@nongnu.org and cc you also myself.
>> But what I received looks like CC ones, no [Qemu-devel] prefix.
> You can tell mailman whether you want to receive copies of mails through
> the list even when you are listed in cc (defaults to on, but some people
> like myself set it off to reduce mail); if you switch that option in
> your subscription settings, then you will not see the [Qemu-devel]
> prefix on any mail where you were cc'd.  [side note: turning off copies
> of mail where you are cc'd triggers what I consider to be a mailman bug:
> it actively rewrites the to/cc of the email to omit your address in the
> copy it sends to the list, which means people who follow up to the list
> no longer cc you, and do not know that you were cc'd in the first place]
I didn't tell mailman anything. So I think the receiving copies setting 
is turned on.
What I can receive is only from cc. But as what Conny said, it seems 
that other external reviewers
in cc list didn't receive any mail unless I replied a mail.
> Furthermore, there may be other places along the way that do data
> de-duplication.  For example, anyone subscribing via a gmail.com address
> gets at most one copy of a message based on the message-id; if they are
> subscribed to the mailing list and also get a cc of a given message,
> only one of those copies will show up (because google suppressed the
> second copy with the same message-id, even though the subject lines are
> different); the one copy is often (but not always) the one without the
> [Qemu-devel] prefix because cc'd mail goes through less processing and
> thus tends to arrive sooner than the copy sent through mailman.  [side
> note: google calls de-duplication a feature, but you can't turn it off,
> and it's one of the reasons that I don't use google for my personal email]
>

  reply	other threads:[~2017-08-28  3:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170823072656.3352-1-zyimin@linux.vnet.ibm.com>
2017-08-24  5:20 ` [Qemu-devel] [PATCH 0/4] four zpci patches Yi Min Zhao
2017-08-24  7:13   ` Cornelia Huck
2017-08-24  8:48     ` Yi Min Zhao
2017-08-24 16:27       ` Eric Blake
2017-08-28  3:26         ` Yi Min Zhao [this message]
2017-08-28  8:04 Yi Min Zhao

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=d47733fa-6f24-1bba-a54f-373a9074c9fd@linux.vnet.ibm.com \
    --to=zyimin@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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).