From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Pei, Yulong" <yulong.pei@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: add section on tested platforms and nics and OSes
Date: Wed, 27 Jul 2016 08:11:40 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025A814D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1469589249-3479-1-git-send-email-yulong.pei@intel.com>
> -----Original Message-----
> From: Pei, Yulong
> Sent: Wednesday, July 27, 2016 4:14 AM
> To: dev@dpdk.org; thomas.monjalon@6wind.com
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Pei, Yulong
> <yulong.pei@intel.com>
> Subject: [PATCH v4] doc: add section on tested platforms and nics and OSes
>
> Add new section on tested platforms and nics and OSes to the release
> notes.
>
> ...
>
> +Tested OSes
> +-----------
> +
> +.. This section should contain a list of OSes that were tested with this
> release.
> +
> + - CentOS 7.0
> + - Fedora 23
> + - Fedora 24
> + - FreeBSD 10.3
> + - Red Hat Enterprise Linux 7.2
> + - SUSE Enterprise Linux 12
> + - Ubuntu 15.10
> + - Ubuntu 16.04 LTS
> + - Wind River Linux 8
> +
Unfortunately, the list of OSes is at the same indentation level as the comment so it is parsed as a comment and isn't visible in the final doc. You can check the doc output as follows:
make doc-guides-html -j
firefox build/doc/html/guides/rel_notes/release_16_07.html &
Just remove the leading whitespace at the start of the list.
Sorry for the rework.
John
prev parent reply other threads:[~2016-07-27 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 3:14 Yulong Pei
2016-07-27 8:11 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2025A814D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yulong.pei@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).