From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: add missing build dependency on librte_net
Date: Fri, 19 Feb 2016 11:24:01 +0100 [thread overview]
Message-ID: <2220699.yF1ID0jGl5@xps13> (raw)
In-Reply-To: <20160219015604.GP21426@yliu-dev.sh.intel.com>
2016-02-19 09:56, Yuanhan Liu:
> On Thu, Feb 18, 2016 at 04:07:52PM +0200, Panu Matilainen wrote:
> > So where do the CC's vanish?
>
> No idea. I also have met this issue __many__ times before: I made a
> group reply, with lots of people CC'ed, later I then received a copy
> (from the mailing list) with all cc list being vanished -- only
> dev@dpdk.org is left. However, I found the CC list was there while
> I checked the sent box.
>
> I was firstly thinking it might be an issue of my email client. However,
> I also found same phenomenon from other's reply. Just not sure whether
> they removed the cc list on purpose or not, though. IIRC, this also
> happened to Bruce (CC'ed).
>
> Anyway, since you have met similar issue just now, I guess it's time to
> shout out and let this issue get noticed, or fixed if there is indeed
> an issue. The mailing list is with high chance being the culprit, IMO.
> Hence, Thomas is CC'ed.
Yes this is due to the "no duplicates" option of mailman:
https://bugs.launchpad.net/mailman/+bug/1216960
I am checking how to disable it.
next prev parent reply other threads:[~2016-02-19 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 9:47 Panu Matilainen
2016-02-18 13:25 ` Yuanhan Liu
2016-02-18 13:39 ` Panu Matilainen
2016-02-18 13:56 ` Yuanhan Liu
2016-02-18 14:07 ` Panu Matilainen
2016-02-19 1:56 ` Yuanhan Liu
2016-02-19 10:24 ` Thomas Monjalon [this message]
2016-02-23 15:34 ` Bruce Richardson
2016-02-18 19:26 ` Thomas Monjalon
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=2220699.yF1ID0jGl5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).