From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
xiao.w.wang@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: add VxLAN GRO to release notes
Date: Fri, 09 Feb 2018 11:02:58 +0100 [thread overview]
Message-ID: <4847510.VVOhfhZ6z7@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EEAD278@IRSMSX103.ger.corp.intel.com>
09/02/2018 10:56, Mcnamara, John:
> The text has been added between the previous section and a note belonging
> to the previous section.
>
> However, we can fix this in the final revision of the release notes, so:
I can fix it.
I also take care of keeping a logical order in release notes features.
For example, drivers are grouped together by class, and libraries are after.
General comment about release notes:
Please try to update release notes while updating the code.
It is better for 3 reasons:
- less chance of forgetting
- release notes is up-to-date in RC1
- it is better linked in the git history
next prev parent reply other threads:[~2018-02-09 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 5:28 Jiayu Hu
2018-02-09 9:56 ` Mcnamara, John
2018-02-09 10:02 ` Thomas Monjalon [this message]
2018-02-13 23:09 ` 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=4847510.VVOhfhZ6z7@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=xiao.w.wang@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).