https://bugzilla.kernel.org/show_bug.cgi?id=37262 --- Comment #33 from Steve <stefan.bosak@xxxxxxxxx> 2011-06-13 14:05:34 --- (In reply to comment #32) > On 06/13/2011 12:55 PM, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > Of course I did bitsect in cloned git directory but i didn't see any output. > > Strange, did you follow the procedure exactly? What's the output after > 'git bisect start'? 1) initial git clone 2) first run git bisect start: no output 3) after second run (git bisect start): Already on 'master' 4) git bisect log: git bisect start 5) git bisect replay: No logfile given 6) git --version: git version 1.7.5.2.317.g391b14.dirty 7) git bisect start v2.6.39-rc1 v2.6.38: Already on 'master' Bisecting: 4616 revisions left to test after this (roughly 12 steps) [179198373cf374f0ef793f1023c1cdd83b53674d] Merge branch 'nfs-for-2.6.39' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6 8) git bisect log: # bad: [0ce790e7d736cedc563e1fb4e998babf5a4dbc3d] Linux 2.6.39-rc1 # good: [521cb40b0c44418a4fd36dc633f575813d59a43d] Linux 2.6.38 git bisect start 'v2.6.39-rc1' 'v2.6.38' 9) git bisect replay: No logfile given It seems initial git bisect start should be run first. > > > I need to try this: > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git > > git bisect start v2.6.39-rc1 v2.6.38 > > perform_make&test > > git bisect bad # i could see info > > git checkout v2.6.39-rc1 > > perform_make&test > > git bisect bad # i could see info > > git checkout v2.6.38 > > perform_make&test > > git bisect good # i could see info > > No need to test v2.6.38 and v2.6.39-rc1 separately, you're already sure > they're good and bad respectively, yes? I need to know exactly what i do to understand it correctly, thank you for your assistance & time investments to help me. I will test it again and give you requested data. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
