patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org, bluca@debian.org
Cc: thomas@monjalon.net, ferruh.yigit@intel.com,
	david.marchand@redhat.com, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-stable] [PATCH 1/2] README: add some example links
Date: Wed, 13 Nov 2019 16:51:18 +0000	[thread overview]
Message-ID: <20191113165119.10807-1-ktraynor@redhat.com> (raw)

Handy to have some example links for easy copy'n'paste
to check the final docs/tarball/git tree.

Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 README | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/README b/README
index 4252285..a4d7a75 100644
--- a/README
+++ b/README
@@ -164,4 +164,7 @@ Example:
   remote: 5e278012506c76d981e4283a92adec1c  /srv/rel/dpdk-18.05.1.tar.xz
 
+You can check the git tree to ensure everything looks good
+- e.g. For DPDK 18.11 https://dpdk.org/browse/dpdk-stable/?h=18.11
+
 You want to prepare a change to the DPDK-web, so grab their repository.
   $ git clone git://dpdk.org/tools/dpdk-web
@@ -169,14 +172,16 @@ You want to prepare a change to the DPDK-web, so grab their repository.
 Modify the file content/download/_index.md
  - update the tarball name
- - check that the link to the documentation really has your tag listed
-   at the top left
+ - e.g. For DPDK 18.11.3 https://fast.dpdk.org/rel/dpdk-18.11.3.tar.xz
  - check that the downloadable tarball matches the md5 listed on the
    git push output
  - add that new md5 to the file
+ - check that the link to the documentation really has your tag listed
+   at the top left
+ - e.g. for DPDK 18.11 releases http://doc.dpdk.org/guides-18.11/
 
 Modify the file content/roadmap/_index.md
  - update the stable releases table for the new versions and dates
 
-and finally suggest the dpdk-web changes to the web team at web@dpdk.org
+and finally send a patch for the dpdk-web changes to the web team at web@dpdk.org
 
 
-- 
2.21.0


             reply	other threads:[~2019-11-13 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 16:51 Kevin Traynor [this message]
2019-11-13 16:51 ` [dpdk-stable] [PATCH 2/2] README: add a few notes about a security release Kevin Traynor
2019-11-13 19:27   ` Luca Boccassi
2019-11-13 19:27 ` [dpdk-stable] [PATCH 1/2] README: add some example links Luca Boccassi

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=20191113165119.10807-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).