On Tue, May 19, 2015 at 2:50 AM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: > > git bisect fix/unfixed sounds interesting though (just > today I tried to find a fix and messed up, again). I am > not aware of the scope you're planning to contribute > to within the git bisect fix/unfixed topic, though I'd like > to share a result[2] of a discussion we had some time > ago, on how git bisect can be improved (nobody did it > yet though). > > [2] https://docs.google.com/document/d/1hzF8fZbsQtKwUPH60dsEwVZM2wmESFq713SeAsg_hkc/edit?usp=sharing It's interesting, but the document doesn't really explain what is not optimal with the current algorithm and why the proposed algorithm is better. Thanks, Christian. -- 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