Grant Likely wrote:
> On 7/14/06, David H. Lynch Jr. wrote:
>
> AFAIK, yes you will have to repatch every time; I typically write a
> little helper script to lessen the pain:
>
> git bisect good|bad # depends on whether it works or not
> patch < [patchfile]
> compile, test, etc
> cg restore -f
On 7/16/06, David H. Lynch Jr. wrote:
> The zlib library was updated within the past month.
> The new zlib code does not work in my environment.
> I have guesses as to why, but I am not a zlib expert and not looking
> to be one.
> I have solved my personal problem by reverting to t
Grant Likely wrote:
> On 6/28/06, David H. Lynch Jr. 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
On 7/14/06, David H. Lynch Jr. wrote:
>
> Thank You git bisect has proven to be incredibly interesting.
>
> One question/problem - maybe an incomplete understanding of git.
>
> What I need to do is get to some version of 2.6.16 - as they all work
> for me.
>
> cut in my patches
Alex Zeffertt wrote:
>
> For diffs of individual files between official kernel releases you can
> use
>
> http://www.linuxhq.com/kernel/
>
> It's really good!
They appear to be updating or something at the moment. I can not get
to most pages.
>
> Alex
>
--
Dave Lynch
Grant Likely wrote:
> On 6/28/06, David H. Lynch Jr. 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 .
David H. Lynch Jr. 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 ?
>
> I guess I can use interdiff to create single patch to go from
> 2.6.16.21 to 2.6.17
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 ?
I guess I can use interdiff to create single patch to go from
2.6.16.21 to 2.6.17 but I am really looking to get all the
On 6/28/06, David H. Lynch Jr. 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 c
