From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] release 16.07.1
Date: Wed, 26 Oct 2016 10:01:11 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6129ACCBB@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <3178910.e9ToaVHYup@xps13>
> -----Original Message-----
> > I'm ok with the split into 2x2 grid, centering the buttons makes the page look better IMO.
> > I can patch after this is applied.
>
> I've sent a v2 with buttons in one row.
> (actually sent 2 times, first on dev@ :/ )
Tested, looks good.
Nit pick, the buttons on rel.html are not centered. I can send a patch after this is applied.
> > Looks like release notes date is being updated, but it still points to the same link?
> No, 16.07 is replaced by 16.07.1 in this list.
> The whole list of every versions is available at http://fast.dpdk.org/rel/
Ok.
> > > - <td><pre>690a2bb570103e58d12f9806e8bf21be</pre></td>
> > > + <td><a href="http://fast.dpdk.org/rel/dpdk-16.07.1.tar.xz">DPDK
> 16.07.1</a></td>
> >
> > It is not clear that this is the stable branch. Would it make more sense to rename to "DPDK
> Stable 16.07.1" or similar to make it more obvious this release has backports/fixes?
>
> I don't think it is needed.
> This list could point only to the latest tar.xz of each major version (16.11, 16.07.1, etc).
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2016-10-26 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 8:11 Yuanhan Liu
2016-10-26 8:58 ` Van Haaren, Harry
2016-10-26 9:54 ` Thomas Monjalon
2016-10-26 10:01 ` Van Haaren, Harry [this message]
2016-10-26 9:48 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2016-10-26 10:13 ` Yuanhan Liu
2016-10-26 10:31 ` [dpdk-web] [PATCH v3] " Thomas Monjalon
2016-10-26 11:08 ` Van Haaren, Harry
2016-10-26 11:17 ` Thomas Monjalon
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=E923DB57A917B54B9182A2E928D00FA6129ACCBB@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@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).