When in dry-run mode, its reasonable to assume that a real release has
not yet been pushed to the remote. Print out the necessary warning/error
messages, but allow the release process to continue so that we can verify
server communication.
Signed-off-by: Jason Gerecke <jason.gere...@wacom.com>
---
release.sh | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/release.sh b/release.sh
index 7370183..7e9bbbe 100755
--- a/release.sh
+++ b/release.sh
@@ -451,8 +451,11 @@ process_module() {
echo " the diff does not contain the string \"$pkg_version\"."
local_top_commit_descr=`git log --oneline --max-count=1
$local_top_commit_sha`
echo " the local top commit is: \"$local_top_commit_descr\""
- cd $top_src
- return 1
+
+ if [ x"$DRY_RUN" = x ]; then
+ cd $top_src
+ return 1
+ fi
fi
fi
@@ -467,8 +470,11 @@ process_module() {
echo "Error: the local top commit has not been pushed to the remote."
local_top_commit_descr=`git log --oneline --max-count=1
$local_top_commit_sha`
echo " the local top commit is: \"$local_top_commit_descr\""
- cd $top_src
- return 1
+
+ if [ x"$DRY_RUN" = x ]; then
+ cd $top_src
+ return 1
+ fi
fi
# If a tag exists with the the tar name, ensure it is tagging the top
commit
--
2.5.3
------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
