Files
git/Doit
Junio C Hamano df5cc80ec9 Introduce an easier to follow "next" branch.
The "pu" branch is a bit too hard to follow.  Let's introduce
"next" branch, which is slightly ahead of "master".  The topic
branches merged into it are not to be rebased, and changes to
the topic branches are first applied to them and then merged
into the "next" branch.  What this means is that the branch is
far easier to follow compared to the "pu" branch since there
will be no rewinding/rebasing involved.
2006-02-08 22:08:30 -08:00

33 lines
525 B
Bash
Executable File

#!/bin/sh
J='-l 1.5 -j'
test -z "$(git diff --cached --name-status)" || {
echo >&2 "Repository unclean."
exit 1
}
Meta/Make clean >/dev/null 2>&1
branches='next master maint'
nstall=install
for branch in $branches
do
if git rev-parse --verify refs/heads/$branch 2>/dev/null
then
echo "* $branch" &&
git checkout $branch &&
Meta/Make $J all &&
Meta/Make $J $nstall &&
Meta/Make test &&
Meta/Make clean &&
nstall=all || exit $?
else
echo "* No $branch"
fi
done >./:all.log 2>&1
git checkout master