[Linux-cachefs] cachefs patches for a recent kernel version?

[alessandro salvatori]

to me GIT commit 3de2403e6659d71b36ec820dc9b942762ddfe6eb seems to be
roughly 2.6.26-rc1-6, albeit that one has a few more commits IIRC, so I
crossed my fingers and applied in the following order:

patch -p1 -i patch-2.6.26-rc1
patch -p1 -i patch-2.6.26-rc1-git6
for i in ../patchset/*.diff; do   echo ==$i==;   patch -p1 --dry-run -i $i;
done

but that hit a few removed files and a few failed hunks. I am tempted to
wiggle around the rejected hunks and give it a try but perhaps it's better
if I just get the right refpoint from git...

Before I go and learn how to checkout with git... I was just wondering, is
this a deliberate choice to provide a patchset against a particular git
commit, as to keep away the vast public from these patches and not expose
them to possibly unstable code?

Thank you!
-Alessandro

On Wed, Jul 2, 2008 at 11:40, alessandro salvatori <sandr8 at gmail.com> wrote:

> I had already tried the patchset 38, but it couldn't apply cleanly to
> 2.6.25.9. What would be the most recent kernel it would apply cleanly to?
>
> thanks!
> -Alessandro
>
>
> On Wed, Jul 2, 2008 at 07:36, David Howells <dhowells at redhat.com> wrote:
>
>> alessandro salvatori <sandr8 at gmail.com> wrote:
>>
>> >    where can I grab cachefs patches that would apply (almost) cleanly
>> > against 2.6.25+ ?
>>
>> Try looking in:
>>
>>        http://people.redhat.com/~dhowells/fscache/patches/<http://people.redhat.com/%7Edhowells/fscache/patches/>
>>
>> David
>>
>
>
>
> --
> A hammer is best when your problem is a nail, and a screwdriver is best
> when your problem is a screw.
>
> A l e s s a n d r o
> S a l v a t o r i




-- 
A hammer is best when your problem is a nail, and a screwdriver is best when
your problem is a screw.

A l e s s a n d r o
S a l v a t o r i