Hi, Le dimanche 2 novembre 2008, Johannes Schindelin a écrit : > Hi, > > On Sun, 2 Nov 2008, Christian Couder wrote: > > This new subcommand should be used when you have a branch or a part of > > a branch that isn't easily bisectable because at some point, say A, a > > bug as been introduced. The bug has been fixed latter at another point, > > say B, but between these points the code is not easily testable because > > of the bug, so it's not easy to bisect between these points. > > Would it not be more intuitive to have support for > > git bisect skip A..B > > ? We can have both. "bisect skip" is about not being able or wanting to test some commits and "bisect replace" is about testing using fixed up branches (that you can share with others) instead of branches that you can't test. When working on big projects where many people are often bisecting (like the Linux kernel), then having shared "bisect-replace" branches (and tags) might save a lot of time to all people bisecting, as they will not have to often skip the same commits or maintain sets of patches to apply when bisecting. 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
