walt <w41ter@xxxxxxxxx> writes: > There are many individual commits from Tejun Heo et al included > in that one big commit from Linus. Unfortunately for me, some of > those commits cause other problems that I'm not trying to bisect; > other problems that evidently get fixed by other commits in the > same big merge. > > So I do 'git bisect skip' six or eight times until the 'false' bug > goes away, and that leaves me at the end of the bisect without finding > the individual commit that's causing my 'real' bug. > > How do you experts handle this kind of problem? If you can identify the commit that fixes the unrelated problem you can try to cherry-pick it during the bisect. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html