There's no particular reason that I see for us needing to enact a 30
second sleep anymore, nor do we have to allocate a pseudo-TTY that
the user then has to manually exit from. Creating a non-interactive
session without sleep seems to work fine now.
Signed-off-by: Jason Gerecke <jason.gere...@wacom.com>
---
release.sh | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/release.sh b/release.sh
index 7e9bbbe..63afa44 100755
--- a/release.sh
+++ b/release.sh
@@ -613,10 +613,11 @@ process_module() {
list_cc=$list_linuxwacom
echo "creating shell on sourceforge for $USER"
- echo "Simply log out once you get to the prompt"
- ssh -t ${USER_NAME%@},linuxwacom@$hostname create
- echo "Sleeping for 30 seconds, because this sometimes helps against
sourceforge's random authentication denials"
- sleep 30
+ ssh ${USER_NAME%@},linuxwacom@$hostname create
+ #echo "Simply log out once you get to the prompt"
+ #ssh -t ${USER_NAME%@},linuxwacom@$hostname create
+ #echo "Sleeping for 30 seconds, because this sometimes helps against
sourceforge's random authentication denials"
+ #sleep 30
fi
# Use personal web space on the host for unit testing (leave commented out)
--
2.5.3
------------------------------------------------------------------------------
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
