From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: restructured release notes documentation
Date: Tue, 11 Aug 2015 13:12:02 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2022E38CE@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <4919431.8QTvr7u91H@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, August 11, 2015 2:02 PM
> To: Mcnamara, John
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: restructured release notes
> documentation
>...
> Why not add faq after user guides and before release notes and
> contributor's guidelines?
> user guides
> faq
> release notes
> contributing
Hi,
No strong reason. I'll submit a V2.
John.
--
next prev parent reply other threads:[~2015-08-11 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 11:57 John McNamara
2015-08-11 13:01 ` Thomas Monjalon
2015-08-11 13:12 ` Mcnamara, John [this message]
2015-08-11 13:28 ` Thomas Monjalon
2015-08-11 15:33 ` 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=B27915DBBA3421428155699D51E4CFE2022E38CE@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).