DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pierre <pierre@emutex.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] dev Digest, Vol 159, Issue 119
Date: Fri, 1 Sep 2017 10:48:38 +0100	[thread overview]
Message-ID: <0d436d2a-78d3-df86-6366-70fb33e9c1f2@intel.com> (raw)
In-Reply-To: <ba6cf0c0-b097-1b77-9c18-c9a6ae2431c0@emutex.com>

Hi Pierre,

On 9/1/2017 10:36 AM, Pierre wrote:
<..>
> 
> 
> On 01/09/17 09:58, dev-request@dpdk.org wrote:
>> Send dev mailing list submissions to
>> 	dev@dpdk.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	http://dpdk.org/ml/listinfo/dev
>> or, via email, send a message with subject or body 'help' to
>> 	dev-request@dpdk.org
>>
>> You can reach the person managing the list at
>> 	dev-owner@dpdk.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of dev digest..."
>>
>>
>> Today's Topics:
>>
>>     1. [PATCH v2 0/3] dynamic linking support (Xiaoyun Li)
>>     2. [PATCH v2 1/3] eal/x86: run-time dispatch over memcpy (Xiaoyun Li)
>>
>>
<...>

Please don't reply back to digest mail!
But reply to the original thread you want to discuss.

If you don't have the original thread, it is possible to get it from
list archive [1], and import it in to your mail client [2] and reply to it.

I agree this is extra work, but good for others and good for discussion.

Thanks,
ferruh

[1]
http://dpdk.org/ml/archives/dev/

[2]
At least Thunderbird supports this.

      reply	other threads:[~2017-09-01  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4135.1504256282.5771.dev@dpdk.org>
2017-09-01  9:36 ` Pierre
2017-09-01  9:48   ` Ferruh Yigit [this message]

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=0d436d2a-78d3-df86-6366-70fb33e9c1f2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=pierre@emutex.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).