Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH] Documentation: bisect: "start" accepts one bad and many good commits

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:03

Christian Couder [off-list ref] writes:
Signed-off-by: Christian Couder <redacted>
Thanks.
+If you know beforehand more than one good commits, you can narrow the
+bisect space down without doing the whole tree checkout every time you
+give good commits. You give the bad revision immediately after `start`
+and then you give all the good revisions you have:
+
+------------
+$ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 --
+                   # v2.6.20-rc6 is bad
+                   # v2.6.20-rc4 and v2.6.20-rc1 are good
 ------------
We would probably want mnemonic to help people remember the
order of parameters: Bad comes before Good, simply because B
sorts earlier than G.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help