DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 17.02
Date: Tue, 14 Feb 2017 16:51:05 +0100	[thread overview]
Message-ID: <1551253.KADGnDBYIu@xps13> (raw)
In-Reply-To: <1487086372-11630-1-git-send-email-john.mcnamara@intel.com>

2017-02-14 15:32, John McNamara:
> -Resolved Issues
> ----------------
> -
> -.. This section should contain bug fixes added to the relevant sections. Sample format:
> -
> -   * **code/section Fixed issue in the past tense with a full stop.**
> -
> -     Add a short 1-2 sentence description of the resolved issue in the past tense.
> -     The title should contain the code/lib section like a commit message.
> -     Add the entries in alphabetic order in the relevant sections below.
> -
> -   This section is a comment. do not overwrite or remove it.
> -   Also, make sure to start the actual text at the margin.
> -   =========================================================
> -
> -
> -EAL
> -~~~
> -
>  
>  Drivers
>  ~~~~~~~
>  
>  * **net/virtio: Fixed multiple process support.**
>  
> -  Fixed few regressions introduced in recent releases that break the virtio
> +  Fixed a few regressions introduced in recent releases that break the virtio
>    multiple process support.
>  
>  
> -Libraries
> -~~~~~~~~~
> -
> -
>  Examples
>  ~~~~~~~~
>  
>  * **examples/ethtool: Fixed crash with non-PCI devices.**
>  
> -  Querying a non-PCI device was dereferencing non-existent PCI data
> -  resulting in a segmentation fault.
> +  Fixed issue where querying a non-PCI device was dereferencing non-existent
> +  PCI data resulting in a segmentation fault.

It looks strange to remove the "Resolved Issues" heading while keeping content.
I think we could totally remove them as most of the fixes are not documented here anyway.

  reply	other threads:[~2017-02-14 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 15:32 John McNamara
2017-02-14 15:51 ` Thomas Monjalon [this message]
2017-02-14 16:22   ` Mcnamara, John
2017-02-14 16:26 ` [dpdk-dev] [PATCH v2] " John McNamara
2017-02-14 20:59   ` 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=1551253.KADGnDBYIu@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 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).