From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Removing the figure and table lists from the documentation
Date: Mon, 16 Nov 2015 13:47:07 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023BCB56@IRSMSX103.ger.corp.intel.com> (raw)
Hi,
The figure and table lists in the documentation are out of date again because some images/tables have been added to the docs without updating the lists.
I could submit a patch to fix this but I would prefer to remove them since they are hard to maintain and not very useful.
If you are wondering about what I am referring to then that is probably a half vote in favour or removing them. See the end of the index sections of:
http://dpdk.org/doc/guides/prog_guide/
http://dpdk.org/doc/guides/sample_app_ug/index.html
http://dpdk.org/doc/guides/nics/index.html
John
next reply other threads:[~2015-11-16 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 13:47 Mcnamara, John [this message]
2015-11-16 14:19 ` Iremonger, Bernard
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=B27915DBBA3421428155699D51E4CFE2023BCB56@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
/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).