On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:Kernel built and installed, so I shall have something to report in the next couple of days.
On Thu, 22 Mar 2007 01:32:36 +0000 Sid Boyce wrote:
...There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
I worked on something over last weekend, but it doesn't really add
much to the references above.
...
FWIW:
My standard instructions for users who are asked to bisect are [1]:
<-- snip -->
# install git and cogito on your computer
# clone Linus' tree:
cg-clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
# start bisecting:
cd linux-2.6
git bisect start
git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round
After at about 8 reboots, you'll have found the guilty commit
("... is first bad commit").
More information on git bisecting:
man git-bisect
<-- snip -->
~Randy
cu
Adrian
[1] the start and end commits and the number of reboots are variable,
but the rest of the text is generic