Only consider xen-[0-9]* as candidates either for returning, or for
matching the current branch.
The effect is that attempts to ask for the `previous Xen branch' of
anything other than a Xen stable branch give the latest Xen stable
branch, which I think is correct.
This fixes a bug where the `previous branch' of xen-unstable-smoke was
considered to be xen-unstable-coverity (!)
This bug would not have been of any consequence, except that the
coverity tested branch name in xen.bit changed in
c/s d94637b6 "coverity: run tests on smoked rather than master"
and had not been created, so that cr-daily-branch would crash for
most branches because the (largely irrelevant) invocation of
`./ap-fetch-version-old xen-unstable-coverity' would fail.
Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
cri-getprevxenbranch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cri-getprevxenbranch b/cri-getprevxenbranch
index a70138e..c4e3ee5 100755
--- a/cri-getprevxenbranch
+++ b/cri-getprevxenbranch
@@ -7,7 +7,7 @@ p=
for b in $(./mg-list-all-branches) ; do # already sorted by version
case "$b" in
- xen*)
+ xen-[0-9]*)
if [ "x$b" = "x$xenbranch" ] ; then
break
else
--
1.7.10.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
