On Fri, Aug 21, 2015 at 8:39 AM, Andreas Schwab <sch...@linux-m68k.org> wrote: > "H.J. Lu" <hjl.to...@gmail.com> writes: > >> up to date by "git merge origin/master". I never tried "git bisect" >> on it since I know that commits on that branch aren't consecutive. > > bisect works with any kind of repository. > >> Also "git bisect" doesn't work on gcc trunk in GCC git mirror >> for commits around wide-int branch merge.
"git bisect good"/"git bisect bad" land my tree not on trunk when they are used on commits from wide-int branch merge. Those commits are 205112 205363 205375 205900 205966 205968 205968 205969 205670 205971 206028 206035 206689 209692 209944 -- H.J.
