From: Panu Matilainen <pmatilai@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Previous DPDK version API documentation for app developers
Date: Thu, 12 Feb 2015 11:55:02 +0200 [thread overview]
Message-ID: <54DC7876.60103@redhat.com> (raw)
In-Reply-To: <2960598.7hMdY0fNP6@xps13>
On 02/12/2015 11:39 AM, Thomas Monjalon wrote:
> 2015-02-12 11:03, Panu Matilainen:
>> On 02/12/2015 09:06 AM, Matthew Hall wrote:
>>> 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.
>>
>> Same goes for release notes: old versions should be kept around and
>> preferably at the original url, which requires them to be versioned from
>> the start.
>
> Panu, release notes are part of the git tree since release 1.8.
>
Sure, but what you find at
http://dpdk.org/browse/dpdk/tree/doc/guides/rel_notes?h=releases&id=v1.8.0
is not very presentable, even if it is readable in the "source" format.
What I mean is ... oh, http://dpdk.org/doc/guides-1.8/ works so it IS
already there, only entirely hidden in the sense that nothing at all
points to the versioned tree AFAICS.
So never mind then :) except perhaps making the versioned docs (API and
all) more visible.
- Panu -
next prev parent reply other threads:[~2015-02-12 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 7:06 Matthew Hall
2015-02-12 9:03 ` Panu Matilainen
2015-02-12 9:39 ` Thomas Monjalon
2015-02-12 9:55 ` Panu Matilainen [this message]
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=54DC7876.60103@redhat.com \
--to=pmatilai@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).