> On 17 Apr 2023, at 15:31, Paul Fertser <fercer...@gmail.com> wrote:
>
> git bisect start; git bisect bad v0.11.0; git bisect good v0.10.0
> ...
> and you can pin-point the offending commit pretty fast
Yes, that's probably the fastest way, since it uses a binary search.
However, using it with the xPack OpenOCD is still tedious, since the build
scripts are intended for building standalone distributions, which means they
always build the dependent libraries from sources and also perform a lot of
post-processing to fix all elf RPATHs, so each iteration may take several good
minutes on a super-fast machine.
But I'm not sure Kristof is prepared to do this.
Liviu
