Re: [PATCH v2 4/7] bisect: add the terms old/new

I agree this makes no sense hardcoding old/new once bisect terms is considerred. It would have been a lot better if we had started implementing bisect terms immediatly (but we thought old/new would already be an appreciable step for most of users). -- To unsubscribe from this list: send the line

[PATCH v2 4/7] bisect: add the terms old/new

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 certain property must be

Re: [PATCH v2 4/7] bisect: add the terms old/new

Antoine Delaite antoine.dela...@ensimag.grenoble-inp.fr writes: Related discussions: - http://thread.gmane.org/gmane.comp.version-control.git/86063 introduced bisect fix unfixed to find fix. - http://thread.gmane.org/gmane.comp.version-control.git/182398