Re: totally confused as to what "git bisect skip" is supposed to do
- Date: Mon, 12 Feb 2018 05:44:54 -0500 (EST)
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Subject: Re: totally confused as to what "git bisect skip" is supposed to do
On Fri, 9 Feb 2018, Junio C Hamano wrote:
> "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx> writes:
> > i'm confused ... why, after skipping a good chunk in the interval
> > [v4.13,v4.14], do i still have exactly 7300 revisions to bisect? what
> > am i so hopelessly misunderstanding here?
> Are you really "skipping" a chunk in the interval?
> I thought that "git bisect skip" is a way for you to respond, when
> "git bisect" gave you a commit to test, saying "sorry, I cannot test
> that exact version, please offer me something else to test". And
> each time you say that, you are not narrowing the search space in
> any way, so it is understandable that the numver of candidate bad
> commits will not decrease.
this might be an issue of terminology, then, as "man git-bisect"
clearly suggests you can skip a range:
You can also skip a range of commits, instead of just one
commit, using range notation. For example:
$ git bisect skip v2.5..v2.6
This tells the bisect process that no commit after v2.5, up to
and including v2.6, should be tested.
my issue (if this is indeed an issue) is that if i select to skip a
sizable range of commits to test, should that not result in git bisect
telling me it now has far fewer revisions to test? if i, in fact,
manage to "disqualify" a number of commits from testing, is there no
visual confirmation that i now have fewer commits to test?