Re: [PATCH v9 4/5] bisect: add the terms old/new

2015-06-26 Thread Matthieu Moy
Christian Couder 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 already

Re: [PATCH v9 4/5] bisect: add the terms old/new

2015-06-25 Thread Christian Couder
On Thu, Jun 25, 2015 at 8:50 PM, Matthieu Moy 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" > +

[PATCH v9 4/5] bisect: add the terms old/new

2015-06-25 Thread Matthieu Moy
From: Antoine Delaite 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' and good': the commits which have a cert