On Mon, Aug 16, 2010 at 12:19 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 08/15/2010 07:15 PM, Teck Choon Giam wrote: >> >> Let me know if I have done anything wrong about the bisecting... ... >> > > All looks fine, but what are the results? git should say something like > 'xxxxxxxxx is first bad commit' which is the interesting part. # git bisect reset master We are not bisecting. # git bisect start # git bisect good # git bisect good qemu-kvm-0.12.1.2 # git bisect bad qemu-kvm-0.12.2 Bisecting: 14 revisions left to test after this (roughly 4 steps) [66dbb62824845e91808171a675998706ce359c71] Handle TFTP ERROR from client # git bisect good Bisecting: 7 revisions left to test after this (roughly 3 steps) [04babf6c6f8ccf69f1219db5fea233d679702e90] roms: rework rom loading via fw # git bisect good Bisecting: 3 revisions left to test after this (roughly 2 steps) [3999bf32440c1ea2ceb85eef008cc56a069af13f] Qemu's internal TFTP server breaks lock-step-iness of TFTP # git bisect good Bisecting: 1 revision left to test after this (roughly 1 step) [e389e937a7b94186449e0590bdc8f04ecbb1ab0b] Update version and changelog for release # git bisect good Bisecting: 0 revisions left to test after this (roughly 0 steps) [b874ce1db7d8654850c8a6606b95ffb1c7d22ce2] Merge remote branch 'upstream/stable-0.12' into stable-0.12 # git bisect bad b874ce1db7d8654850c8a6606b95ffb1c7d22ce2 is the first bad commit Thanks. Kindest regards, Giam Teck Choon -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
