Re: how to get individual patches

["Grant Likely" <grant.likely@secretlab.ca>]

On 6/28/06, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
>
>     The bsp I am working on works with 2.6.16.21 but fails with 2.6.17.
>
>     How can I find the individual patches that make up the transition
> from 2.6.16.21 to 2.6.17 ?

Unfortunately, there isn't a direct line between .16.21 and .17 which
makes it complicated.  Does your bsp work with .16?  If so; you can
use the 'git bisect' command to figure out exactly where the
regression occured.

If it doesn't work on .16; you can do a bisect between .16 and .16.21
to figure out what patch is missing between .16 and .17.

$ git bisect good v2.6.16
$ git bisect bad           # the head of the tree
compile, test, etc.
$ git bisect good|bad    # depends on whether it works or not
compile, test, etc
$ git bisect good|bad    # you get the idea... repeat until it's narrowed down
$ git log                          # see where you are in the git tree.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195