On Mon, Feb 17, 2020 at 5:32 PM Andy Shevchenko <[email protected]> wrote: > On Mon, Feb 17, 2020 at 5:09 PM Wolfgang Denk <[email protected]> wrote: > > In message > > <cahp75vduy7zjfkc4yv-ktt1aekg9ggy6psjaeokgo9ectqx...@mail.gmail.com> you > > wrote: > > > > > > > > git bisect is the usual way to figure out the culprit. > > > > > > > > Too much work to do this way. > > > > If you find bisecting is too much work you probably still do it > > manually. Why don't you use tbot to automize such boring and time > > consuming tasks? > > Bisection time something about 10%, while 90% is flashing the board > and, given the result, triggering either bad or good next cycle.
And btw, doing git bisect is not mandatory technique to follow as long as I can guarantee the (reproducible) result, right? -- With Best Regards, Andy Shevchenko
