fi
export RUN_ALL_TESTS=true
+# clean up any old home storage paths.
+\rm -rf "$feisty_path/home_store".*
+# set home folder to a new home_store.random folder, for anything that
+# feisty meow needs to store under $HOME.
export HOME="$(mktemp -d "$feisty_path/home_store.XXXXXX")"
cd "$feisty_path"
export FEISTY_MEOW_APEX="$(\pwd)"
#maybe they unbroke it in 17.10? yes, but it requires NO space now. *&@#*&@#
#hmmm: bring back old version but check for ubuntu 17.04 vs 17.10 now.
#actually they made it a new parm. arghhh!
- screen -L $boguslog -S "$screen_name" -d -m nice -n $NICENESS_LEVEL mono "$app_name"
+ screen -L -S "$screen_name" -d -m nice -n $NICENESS_LEVEL mono "$app_name"
+#$boguslog
echo "$(date_stringer ' '): $screen_name started."
# only sleep if we are not at the last process that gets started.
remote_branch_info=$(git ls-remote --heads origin $bran 2>/dev/null)
if [ ! -z "$remote_branch_info" ]; then
# we are pretty sure the remote branch does exist.
- git pull $PULL_ADDITION origin "$bran" | $TO_SPLITTER
+ git pull --tags $PULL_ADDITION origin "$bran" | $TO_SPLITTER
# we may want to choose to do fast forward, to avoid crazy multiple merge histories
# without any changes in them. --no-ff
promote_pipe_return 0
# now pull down any changes in our own origin in the repo, to stay in synch
# with any changes from others.
- git pull $PULL_ADDITION --all | $TO_SPLITTER
+ git pull --tags $PULL_ADDITION --all | $TO_SPLITTER
#is the above really important when we did this branch already in the loop?
#it does an --all, but is that effective or different? should we be doing that in above loop?
# --no-ff
elif [ -d ".git" ]; then
if test_writeable ".git"; then
$blatt
- git pull $PULL_ADDITION 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
+ git pull --tags $PULL_ADDITION 2>&1 | grep -v "X11 forwarding request failed" | $TO_SPLITTER
#ordinary pulls should be allowed to do fast forward: --no-ff
promote_pipe_return 0
test_or_die "git pull of origin"