From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: [dpdk-dev] Previous DPDK version API documentation for app developers
Date: Wed, 11 Feb 2015 23:06:35 -0800 [thread overview]
Message-ID: <20150212070635.GA31227@mhcomputing.net> (raw)
Hi all,
I ran into a funny situation today with the API documentation.
For stability until I can get my app mostly working, I was using DPDK 1.7.X,
so I could concentrate on making the app reliable. But the DPDK website only
has the API docs for DPDK 1.8.X / HEAD.
I was wondering if we could have copies of the most recent few versions in the
site, and some scripts or steps to regenerate locally so you can get the
matching version in the local machine.
This would also help me to do some suppoert things for our community, like
making small patches to fix parts of the docs with typos / formatting bugs.
With the steps how to generate them right, I could fix docs bugs in the
sources and make sure the docs read right afterward for others.
Thanks,
Matthew.
next reply other threads:[~2015-02-12 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 7:06 Matthew Hall [this message]
2015-02-12 9:03 ` Panu Matilainen
2015-02-12 9:39 ` Thomas Monjalon
2015-02-12 9:55 ` Panu Matilainen
2015-02-12 9:29 ` Thomas Monjalon
2015-02-17 8:48 ` Matthew Hall
2015-02-17 9:30 ` Thomas Monjalon
2015-02-17 9:33 ` Matthew Hall
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=20150212070635.GA31227@mhcomputing.net \
--to=mhall@mhcomputing.net \
--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).