RE: Linux 2.2.20pre11

[Lakey, Jeremy # IHTUL]

>> 1) publish a patch (ie. telling us all the changes)
>> 2) describe the set of changes which are not security
>>    related (ie. telling us the non-security related
>>    changes)
>> 
>> By deduction aren't you in fact "telling us what the secutiry related 
>> changes are"? :-)
>
>Not directly, and if you have enough skill to work through the code you
could do so anyway. Whether reading >the source code for that purpose is
legal I don't know.
>
>Have fun
>
>Alan

So those of us in the USA are free to run a diff on cvs ourselves, document
the changes, and publish our findings.  *shrug*