Christian Couder christian.cou...@gmail.com writes:
So perhaps you could use a function like:
write_bisect_terms() {
if test ! -s $GIT_DIR/BISECT_TERMS
then
echo $NAME_BAD $GIT_DIR/BISECT_TERMS
echo $NAME_GOOD $GIT_DIR/BISECT_TERMS
fi
}
I
From: Antoine Delaite antoine.dela...@ensimag.grenoble-inp.fr
When not looking for a regression during a bisect but for a fix or a
change in another given property, it can be confusing to use 'good'
and 'bad'.
This patch introduce `git bisect new` and `git bisect old` as an
alternative to 'bad'
On Thu, Jun 25, 2015 at 8:50 PM, Matthieu Moy matthieu@imag.fr wrote:
[...]
@@ -178,7 +183,7 @@ bisect_start() {
}
git rev-parse --sq-quote $@ $GIT_DIR/BISECT_NAMES
eval $eval true
- if test $revision_seen -eq 1 test ! -s $GIT_DIR/BISECT_TERMS
+
3 matches
Mail list logo