> Hi Michael,
>
> You're certainly well-known. welcome to KGDB!
>
> I am afraid locating a patch set in cvs for 2.6.17.7 is going to be
difficult.
>
> File: core-lite.patch   Status: Up-to-date
>
>    Working revision:    1.128
>    Repository revision: 1.128   /cvsroot/kgdb/kgdb-2/core-lite.patch,v
>    Sticky Tag:          (none)
>    Sticky Date:         (none)
>    Sticky Options:      (none)
>
>         linux2_6_24_uprev               (branch: 1.128.2)
>         linux2_6_23_uprev               (branch: 1.126.2.14.4)
>         linux2_6_22_uprev               (branch: 1.127.2)
>         linux2_6_17                     (revision: 1.126)
>         linux2_6_21_uprev               (branch: 1.126.2)
>         kgdb_2_4                        (branch: 1.121.2)
>
> The closest is linux2_6_17. Other than this and the email archives, there
is
> no more information. You'll need to apply these patches by hand.

OK, thanks, but they don't even seem close.
Any hints appreciated.

Should I start from the kernel.org tree, or the linux-mips.org tree?

Can you give me the approximate date when the linux2_6_17 tag was created?

Can  you guestimate which sub-release of 2.6.17 the tag would correspond to?


If I knew whether to go forward or backward in the cvs history, it
would cut the task in half...




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to