From: Bruce Richardson <bruce.richardson@intel.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: Tue, 23 Feb 2016 15:34:45 +0000 [thread overview]
Message-ID: <20160223153445.GA15208@bricha3-MOBL3> (raw)
In-Reply-To: <20160219015604.GP21426@yliu-dev.sh.intel.com>
On Fri, Feb 19, 2016 at 09:56:04AM +0800, Yuanhan Liu wrote:
> On Thu, Feb 18, 2016 at 04:07:52PM +0200, Panu Matilainen wrote:
> > >I didn't see the author was cc'ed from my email client:
> > >
> > > Date: Thu, 18 Feb 2016 11:47:43 +0200
> > > From: Panu Matilainen <pmatilai@redhat.com>
> > > To: dev@dpdk.org
> > > Subject: [dpdk-dev] [PATCH] vhost: add missing build dependency on librte_net
> >
> > Hmm, indeed. But this is what git told me (happened to have the whole thing
> > in scrollback buffer):
> >
> > [pmatilai@sopuli dpdk]$ git send-email --cc="jijiang.liu@intel.com"
> > --cc="huawei.xie@intel.com" -1
> > /tmp/ZAW8ErlHWe/0001-vhost-add-missing-build-dependency-on-librte_net.patch
> >
> > From: Panu Matilainen <pmatilai@redhat.com>
> > To: dev@dpdk.org
> > Cc: jijiang.liu@intel.com,
> > huawei.xie@intel.com
> > Subject: [PATCH] vhost: add missing build dependency on librte_net
> > Date: Thu, 18 Feb 2016 11:47:43 +0200
> > Message-Id:
> > <eef2b50186eea076a3a3ff9f10bd8c310a036549.1455788863.git.pmatilai@redhat.com>
> > X-Mailer: git-send-email 2.5.0
> >
> > Send this email? ([y]es|[n]o|[q]uit|[a]ll): a
> > OK. Log says:
> > Server: smtp.corp.redhat.com
> > MAIL FROM:<pmatilai@redhat.com>
> > RCPT TO:<dev@dpdk.org>
> > RCPT TO:<jijiang.liu@intel.com>
> > RCPT TO:<huawei.xie@intel.com>
> > From: Panu Matilainen <pmatilai@redhat.com>
> > To: dev@dpdk.org
> > Cc: jijiang.liu@intel.com,
> > huawei.xie@intel.com
> > Subject: [PATCH] vhost: add missing build dependency on librte_net
> > Date: Thu, 18 Feb 2016 11:47:43 +0200
> > Message-Id:
> > <eef2b50186eea076a3a3ff9f10bd8c310a036549.1455788863.git.pmatilai@redhat.com>
> > X-Mailer: git-send-email 2.5.0
> >
> > 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).
>
And I thought it was just me! :-)
/Bruce
next prev parent reply other threads:[~2016-02-23 15:34 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
2016-02-23 15:34 ` Bruce Richardson [this message]
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=20160223153445.GA15208@bricha3-MOBL3 \
--to=bruce.richardson@intel.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).