cri-common, ap-*: use >&2 with git-clone, git-fetch to avoid ap-* producing spurious...

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>

diff --git a/ap-fetch-version b/ap-fetch-version
index 257547f4dc4d31c46bb748a0010d41a4bdcfae4a..1f3c6e97f1d1cd69e4c768c18032f8fd6ae16ab4 100755 (executable)
--- a/ap-fetch-version
+++ b/ap-fetch-version
@@ -70,7 +70,7 @@ linuxfirmware)
                $UPSTREAM_TREE_LINUXFIRMWARE master daily-cron.$branch
        ;;
 osstest)
-       git-fetch $HOME/testing.git pretest:ap-fetch
+       git-fetch $HOME/testing.git pretest:ap-fetch >&2
         git-rev-parse ap-fetch^0
         ;;
 *)

diff --git a/cri-common b/cri-common
index 043b9fe0bdfb513701e1fe32d148c335fcc3f370..477b013450c90b70ca7a0a69dbfa068561546805 100644 (file)
--- a/cri-common
+++ b/cri-common
@@ -28,10 +28,10 @@ repo_tree_rev_fetch_git () {
        local localtag=$4
        local realurl="`getconfig GitCacheProxy`$remoteurl"
        if ! test -d $repos/$treename; then
-               git clone --bare $realurl $repos/$treename
+               git clone --bare $realurl $repos/$treename >&2
        fi
        cd $repos/$treename
-       git fetch -f $realurl $remotetag:$localtag
+       git fetch -f $realurl $remotetag:$localtag >&2
        git-rev-parse $localtag^0
 }