patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: stable@dpdk.org
Cc: ktraynor@redhat.com
Subject: [dpdk-stable] [PATCH stable-scripts 2/2] Make failed_list and known_issues optional
Date: Tue, 17 Mar 2020 10:19:14 +0000	[thread overview]
Message-ID: <20200317101914.19443-2-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20200317101914.19443-1-luca.boccassi@gmail.com>

From: Luca Boccassi <luca.boccassi@microsoft.com>

Some releases don't have them
---
 5-make-release-commit | 26 ++++++++++++++------------
 6-announce-release    | 19 ++++++++++---------
 2 files changed, 24 insertions(+), 21 deletions(-)

diff --git a/5-make-release-commit b/5-make-release-commit
index 4926ab1..832e8e4 100755
--- a/5-make-release-commit
+++ b/5-make-release-commit
@@ -43,19 +43,21 @@ update_release_note()
 
 	echo "$(cat $stable_release/validation)"
 
-        echo
-        echo "$stable_release Known Issues"
-        echo "~~~~~~~~~~~~~~~~~~~~"
-        echo
+	if [ -e $stable_release/known_issues ]; then
+		echo
+		echo "$stable_release Known Issues"
+		echo "~~~~~~~~~~~~~~~~~~~~"
+		echo
+		echo "$(cat $stable_release/known_issues)"
+	fi
 
-	echo "$(cat $stable_release/known_issues)"
-
-        echo
-        echo "$stable_release Fixes skipped and status unresolved"
-        echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"
-        echo
-
-	echo "$(cat $stable_release/failed_list)"
+	if [ -e $stable_release/failed_list ]; then
+		echo
+		echo "$stable_release Fixes skipped and status unresolved"
+		echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"
+		echo
+		echo "$(cat $stable_release/failed_list)"
+	fi
 
 	} >> $DPDK_DIR/doc/guides/rel_notes/release_${RTE_VER_MAJOR/./_}.rst
 }
diff --git a/6-announce-release b/6-announce-release
index 0a7a4fc..6d9fb86 100755
--- a/6-announce-release
+++ b/6-announce-release
@@ -2,13 +2,11 @@
 
 source ./lib.sh
 
-if [ $# -lt 1 ] || [ ! -f "$1" ]
+if [ $# -ge 1 ]
 then
-	echo "Usage: $0 failed_list"
-	exit 1
+	failed_list="/tmp/.list-$$"
+	grep -v "^#" $1 > $failed_list
 fi
-failed_list="/tmp/.list-$$"
-grep -v "^#" $1 > $failed_list
 
 get_diffs()
 {
@@ -44,7 +42,9 @@ EOF
 
 compose_release_note
 
-cat << EOF
+if [ $# -ge 1 ]
+then
+	cat << EOF
 ---[ List of missing patches ]---
 The following is the accumulated list of skipped patches. Authors/maintainers
 have not yet responded to backport requests. Actions to take per each patch,
@@ -53,6 +53,7 @@ have not yet responded to backport requests. Actions to take per each patch,
 	b) send out a backport to stable@dpdk.org
 
 EOF
-while read commit patch; do
-	describe_commit $commit
-done < $failed_list | sort -k 2
+	while read commit patch; do
+		describe_commit $commit
+	done < $failed_list | sort -k 2
+fi
-- 
2.20.1


  reply	other threads:[~2020-03-17 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 10:19 [dpdk-stable] [PATCH stable-scripts 1/2] Update version mangling luca.boccassi
2020-03-17 10:19 ` luca.boccassi [this message]
2020-03-18 12:08   ` [dpdk-stable] [PATCH stable-scripts 2/2] Make failed_list and known_issues optional Kevin Traynor
2020-03-18 12:15 ` [dpdk-stable] [PATCH stable-scripts 1/2] Update version mangling Kevin Traynor
2020-03-18 12:47 ` Kevin Traynor

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=20200317101914.19443-2-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@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).