From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] doc: add VxLAN GRO to release notes Date: Fri, 09 Feb 2018 11:02:58 +0100 Message-ID: <4847510.VVOhfhZ6z7@xps> References: <1518154117-81882-1-git-send-email-jiayu.hu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "Hu, Jiayu" , "dev@dpdk.org" , xiao.w.wang@intel.com To: "Mcnamara, John" Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 37E9F1B836 for ; Fri, 9 Feb 2018 11:03:08 +0100 (CET) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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