From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [RFC] location for DPDK related white papers
Date: Fri, 23 Oct 2015 15:41:21 +0200 [thread overview]
Message-ID: <1560743.lPy8AhS6XF@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20238CF0A@IRSMSX103.ger.corp.intel.com>
2015-10-23 10:28, Mcnamara, John:
> We have had a few people wishing to submit DPDK related white papers.
> These tend to focus on particular aspects of DPDK and don't fit into
> any of the existing documents.
>
> Where should these be stored/made available? Some options:
>
> * In the repo, in RST format in a doc/guides/white_paper directory.
> * On dpdk.org in PDF format.
> * Elsewhere.
>
> Any comments, suggestions?
I would like to comment but I don't really know what means "white papers".
Why not ask the question while submitting such document?
next prev parent reply other threads:[~2015-10-23 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 10:28 [RFC] location for DPDK related white papers Mcnamara, John
2015-10-23 13:41 ` Thomas Monjalon [this message]
2015-10-23 14:48 ` Mcnamara, John
2015-10-23 14:52 ` Thomas Monjalon
2015-10-23 13:48 ` Jay Rolette
2015-10-23 15:07 ` Dave Neary
2015-10-23 16:19 ` Marc
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=1560743.lPy8AhS6XF@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.