From 2fd5c2dcc07d9ebadf17489befc521367ea889a1 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Thu, 21 Nov 2013 12:24:06 +0000 Subject: [PATCH] cri-common, ap-*: use >&2 with git-clone, git-fetch to avoid ap-* producing spurious messages on stdout Signed-off-by: Ian Jackson --- ap-fetch-version | 2 +- cri-common | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ap-fetch-version b/ap-fetch-version index 257547f..1f3c6e9 100755 --- 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 043b9fe..477b013 100644 --- 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 } -- 2.39.5