dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Panu Matilainen <pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Previous DPDK version API documentation for app developers
Date: Thu, 12 Feb 2015 10:39:35 +0100	[thread overview]
Message-ID: <2960598.7hMdY0fNP6@xps13> (raw)
In-Reply-To: <54DC6C5C.6020005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

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.

  parent reply	other threads:[~2015-02-12  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  7:06 Previous DPDK version API documentation for app developers Matthew Hall
     [not found] ` <20150212070635.GA31227-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-02-12  9:03   ` Panu Matilainen
     [not found]     ` <54DC6C5C.6020005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-12  9:39       ` Thomas Monjalon [this message]
2015-02-12  9:55         ` Panu Matilainen
2015-02-12  9:29   ` Thomas Monjalon
2015-02-17  8:48     ` Matthew Hall
     [not found]       ` <ECEEF3EE-01F5-48A4-BC9D-F980FB39B604-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
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=2960598.7hMdY0fNP6@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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).