From: Robert P. J. Day <rpjday@crashcourse.ca>
Date: Fri, 09 Feb 2018 20:54:37 GMT
Subject: Re: "git bisect run make" adequate to locate first unbuildable commit?
Message-ID: <alpine.LFD.2.21.1802091553290.17104@localhost.localdomain>
In-Reply-To: <9803DEA99A6545F7A3F9A3CE08FE2263@PhilipOakley>

On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote:

> From: "Robert P. J. Day" <rpjday@crashcourse.ca>
> >
> > writing a short tutorial on "git bisect" and, all the details of
> > special exit code 125 aside, if one wanted to locate the first
> > unbuildable commit, would it be sufficient to just run?
> >
> >  $ git bisect run make
> >
> > as i read it, make returns either 0, 1 or 2 so there doesn't appear
> > to be any possibility of weirdness with clashing with a 125 exit code.
> > am i overlooking some subtle detail here i should be aware of? thanks.
> >
> > rday
>
> In the spirit of pedanticism, one should also clarify the word
> "first", in that it's not a linear search for _an_ unbuildable
> commit, but that one is looking for the transition between an
> unbroken sequence of unbuildable commits, which transitions to
> buildable commits, and its the transition that is sought. (there
> could be many random unbuildable commits within a sequence in some
> folks' processes!)

  quite so, i should have been more precise.

rday