On Sun, 2010-03-07 at 14:29 -0800, Junio C Hamano wrote: > * "git bisect -- pathspec..." did not diagnose an error condition properly when > the simplification with given pathspec made the history empty. Would that be what led to this somewhat less than perfect tip bisection result? I had to repeat, leaving off the pathspec, in order to bisect to the troublesome commit. b4dad12cdd22f61eb093d23f11a7b09620e53aba is the first bad commit git bisect start '--' 'tools/perf' # good: [64ba9926759792cf7b95f823402e2781edd1b5d4] Merge branch 'for-linus' of git://git.open-osd.org/linux-open-osd git bisect good 64ba9926759792cf7b95f823402e2781edd1b5d4 # bad: [a8313ee914acb061cacb44d0884e448760e33392] Merge branch 'perf/pebs' git bisect bad a8313ee914acb061cacb44d0884e448760e33392 # good: [eaa5eec739637f32f8733d528ff0b94fd62b1214] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp git bisect good eaa5eec739637f32f8733d528ff0b94fd62b1214 # bad: [b9377fc0bf1cd0b7b494337eacf8ccf0f7b52e1f] Merge branch 'perf/probes' git bisect bad b9377fc0bf1cd0b7b494337eacf8ccf0f7b52e1f # bad: [318794793ce30dc7000ed6992f4f81f308ae3958] manual merge of linus git bisect bad 318794793ce30dc7000ed6992f4f81f308ae3958 # good: [617f757a1b45395ca3b11b162138ce514afc5b29] Merge branch 'perf/core' git bisect good 617f757a1b45395ca3b11b162138ce514afc5b29 # good: [c93025db5f6d093fd00e96fde8e47d5c791a03fd] Merge branch 'perf/core' git bisect good c93025db5f6d093fd00e96fde8e47d5c791a03fd # good: [eb3addcb8fe9b81f47ad0f14ed0ae220f18ae83b] Merge branch 'perf/urgent' git bisect good eb3addcb8fe9b81f47ad0f14ed0ae220f18ae83b # bad: [b4dad12cdd22f61eb093d23f11a7b09620e53aba] Merge branch 'core/iommu' git bisect bad b4dad12cdd22f61eb093d23f11a7b09620e53aba -- 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