Comment # 3
on bug 92858
from Darren
I downloaded the kernel source via git, using "git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git," then I changed directory into the folder it created, called "linux." I then ran "git bisect start v4.2 v4.1" and the output was: "Bisecting: 7353 revisions left to test after this (roughly 13 steps) [c11d716218910c3aa2bac1bb641e6086ad649555] Merge tag 'armsoc-cleanup' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc" I'm not to up to speed on git bisect, but don't I need to declare a good revision first so bisect has somewhere to start? Also, in order to declare a good revision, I'd need to compile the whole kernel again starting with the initial git commit during the 4.2 merge window, wouldn't I? The above "git clone" command checks out the source for the latest kernel (not sure about which if any kernel history it downloads,) no? And if I compile using it, wouldn't it build 4.3.0 instead of an earlier revision? To summarize, I'm very much a newcomer to git--if I needed to install a kernel before, I would use AUR packages, or in the case of beginner friendly distributions like Ubuntu, would simply grab the latest kernel from a PPA. I can copy and paste commands, learned what "--depth=X" does-in the event I needed to download without history-while building the nouveau kernel tree back when I had a nVidia GPU, but I'm not otherwise too experienced. Can you point me to the best resource/s on learning git and how to identify what those long strings of text like "c11d716218910c3aa2bac1bb641e6086ad649555" indicate and what to do to isolate a good revsion so bisect can start at it? Thanks!
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
