On Wed, 2011-05-25 at 16:38 -0500, Jonathan Nieder wrote: [...] > + Build and test a binary package as explained in > + <ref id="common-building">: > + <example> > +$ make deb-pkg > +$ cd .. > +# dpkg -i *.deb This last command is not generally a good idea! > +# reboot > + </example> > + If the bug doesn't show up, try again with the standard > + configuration file from /boot. (If it still doesn't show up > + after that, declare victory and celebrate.) s/standard/official/ > + </p> > + > + <p> > + Initialize the bisection process by declaring which versions worked > + and did not work: > + <example> > +$ cd linux-2.6 > +$ git bisect start > +$ git bisect bad; # current version is bad > +$ git bisect good v2.6.12; # or whichever was known to be good [...] You can specify the initial bad and good versions on the same command. 'Common tasks' is a big chapter already, and I'm not sure that bisection is that common. This might be better placed in the 'bugs' chapter. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part