On Wed, 1 Jul 2009 17:12:16 +0000 (UTC) Robert Stonehouse <rstonehouse@xxxxxxxxxxxxxx> wrote: > $ git log --graph --abbrev-commit --pretty=oneline > * b394c57... master4 > * 7e8d675... Merge branch 'featureB' > |\ > | * 8d87aee... featureB2 > | * c1a8450... featureB1 > * | 44c5601... master3 > * | 269602a... Merge branch 'featureA' > |\ \ > | * | 91b1bbb... featureA2 > | * | 0c15834... featureA1 > | |/ > * | 1ea4a0c... master2 > |/ > * 204f839... master1 > > Tag featureA1 was my good commit, and HEAD was the bad. > I was surprised that git bisect was asking me to test commits on the featureB > branch. I couldn't test the build target that was broken on branch featureB > because it wasn't present in the code at that point. You can exclude the featureB branch by listing at good. Git will know there is no need to test anything on that branch: $ git bisect start HEAD featureA1 featureB2 HTH, Sean -- 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