@@ -54,7 +54,7 @@ xen-4.*-testing)
$TREE_XEN staging-$branchcore $LOCALREV_XEN
;;
xen-unstable-coverity)
- repo_tree_rev_fetch_git xen $TREE_XEN smoked $LOCALREV_XEN
+ repo_tree_rev_fetch_git xen $TREE_XEN smoke $LOCALREV_XEN
;;
qemu-mainline)
repo_tree_rev_fetch_git $branch \
@@ -60,7 +60,7 @@ xen-4.*-testing)
$TREE_XEN stable-$branchcore $LOCALREV_XEN
;;
xen-unstable-coverity)
- repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/smoked $LOCALREV_XEN
+ repo_tree_rev_fetch_git xen $TREE_XEN coverity-tested/smoke $LOCALREV_XEN
;;
qemu-mainline)
repo_tree_rev_fetch_git $branch \
@@ -70,7 +70,7 @@ xen-*-testing)
;;
xen-unstable-coverity)
cd $repos/xen
- git push $TREE_XEN $revision:refs/heads/coverity-tested/smoked
+ git push $TREE_XEN $revision:refs/heads/coverity-tested/smoke
;;
qemu-mainline)
cd $repos/qemu-mainline
c/s d94637b6 "coverity: run tests on smoked rather than master" used `smoked' in several places, including as the name of the input branch (which is already established as `smoke'), and the name of the coverity-tested branch. But we call this `smoke', not `smoked'. After this patch `git-grep smoked' produces no output, as it did in d94637b6~. Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com> --- ap-fetch-version | 2 +- ap-fetch-version-old | 2 +- ap-push | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)