Leann Ogasawara wrote: > The best approach to isolating patches which resolved the issue for > Intrepid would be to do a git bisect. This is obviously not something > we expect you to know how to do so this is completely at your own > discretion if you'd like to try. The following link describes how to > perform a git bisect: > > http://www.kernel.org/doc/local/git-quick.html#bisect
I've read the whole document, but do not understand it very well yet. > The only tricky issue is you're going to have to reverse the meanings of > good and bad since you're trying to isolate a patch which fixed the > issue, and not caused a regression. You can get the Intrepid git tree > by doing: > > git clone git://kernel.ubuntu.com/ubuntu/ubuntu-intrepid.git ubuntu- > intrepid Yes, I ran that command successfully. However, I am not sure how to run the git bisect... I now have a directory called "ubuntu-intrepid" with a lot of subdirectories under it. I can see that if I run "git bisect bad", this will establish the current version of intrepid (aka master) as faulty (but in my case good). I don't know what to use as the "good" version. Does my intrepid git hold enough history to go back to the hardy kernel? I tried "git bisect good release_2_6_24", but got the error message "bad rev input" and wasn't very surprised. I can see from the makefile that the current (intrepid) version is 2_6_27, but scratching around the directory hasn't shown me what to use as the correct name for hardy - should I have also done a clone of ubuntu-hardy-git into a different directory and then done a bisect between these two? Even if yes, I still need to know what name to use for the current Hardy kernel version. Sorry to have to ask for help, but I need to get past the crud I don't understand quickly so that I can devote my attention to the real problem! Thanks in anticipation... Brian -- CUPS does not print to LPD printer https://bugs.launchpad.net/bugs/213081 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
