Hi Christian, On Wed, 15 Feb 2017, Christian Couder wrote: > On Tue, Feb 14, 2017 at 10:08 PM, Junio C Hamano <gitster@xxxxxxxxx> > wrote: > > > Probably a less resource intensive approach is to find the tips of the > > topics not in 'next' but in 'pu' and test them. That would give you > > which topic(s) are problematic, which is a better starting point than > > "Oh, 'pu' does not build". After identifying which branch is > > problematic, bisection of individual topic would be of more manageable > > size. > > It is still probably more resource intensive than it couls be. Indeed. Ciao, Dscho