Comment # 37 on bug 1193652 from Ben Thomas George

(In reply to Oliver Neukum from comment #36)
> (In reply to Ben Thomas George from comment #35)
> > (In reply to Oliver Neukum from comment #34)
> > > (In reply to Ben Thomas George from comment #33)
> > > 
> > > > What do you mean by bisect?
> > > 
> > > This refers to the "git bisect" command which checks out the kernel in the
> > > middle between a known good and a known bad version, which you compile and
> > > test and theb repeat the process until you end up with the change that has
> > > caused a regression.
> > 
> > I am actually not very familiar with tech. Only know the basics to run it as
> > a daily driver.
> > 
> > If you could instruct me step by step I could attempt this.
> 
> OK, we can try. Thank you for doing this big jump. The original is
> documented here:
> http://events17.linuxfoundation.org/sites/events/files/slides/
> Enjoy%20Fighting%20regressions%20with%20git%20bisect%2C%20LinuxCon%20EU%20201
> 3.pdf
> 
> You'd start with cloning the stable tree:
> 
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> linux-stable
> 
> This will give you a directory with the stable tree. You enter that
> directory and do
> 
> git bisect start ; git bisect good v5.15.5 ; git bisect bad v5.15.7
> 
> This will give you the first kernel tree to compile. Do you know how to
> compile a kernel?

No, I will haven't compiled the kernel yet.

So the first step is cloning the stable tree -that is the kernel?