On Fri, 9 Feb 2018, Philip Oakley wrote:
> From: "Robert P. J. Day"
> > On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote:
> (apologies for using the fancy letters after the name ID...)
> >
> >> From: "Robert P. J. Day"
> >> >
> >> > writing a
> > 1. there may be feature branches that bypass the known good starting
> >commit, which can cause understanding issues as those side
> >branches that predate the start point are also considered
> >potential bu commits.
>
> ok, but let's make sure i understand what defines a
On Fri, 9 Feb 2018, Philip Oakley wrote:
> From: "Robert P. J. Day"
> > On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote:
> (apologies for using the fancy letters after the name ID...)
> >
> >> From: "Robert P. J. Day"
> >> >
> >> > writing a
From: "Robert P. J. Day"
On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote:
(apologies for using the fancy letters after the name ID...)
From: "Robert P. J. Day"
>
> writing a short tutorial on "git bisect" and, all the details of
> special
From: "Robert P. J. Day"
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
On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote:
> From: "Robert P. J. Day"
> >
> > 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
On Fri, Feb 9, 2018 at 2:20 PM, Robert P. J. Day wrote:
>
> 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
7 matches
Mail list logo