> Sorry, I assumed that 80% and 86% were close enough that a reasonable reader would be able > to see that I had mis-remembered the second significant figure for statistics I heard a while ago. vs. >>and the source of…
> Sorry, it's 86% and 14% in Linux 4.11. It's literally in the link I posted. you first quoted 80% and chided me for not reading the article linked to because it supposedly implied/had it in there. now you're moving the…
> 1000 small commits can add up to 100 small+simple components vs. > Commits might be patches, but they're sure not components. make up your mind, are components (whatever that means for you) composed of commits or not?…
and the source of those numbers is...? > As for grsecurity, 100% of the core grsecurity team (that work at "Open Source Security") are paid for their work. that's 100% false. both spender and me are developing our code…
careful there, the author line doesn't imply authorship (if it does, the upstream kernel is already violating our copyrights).
i don't quite get what you're arguing now... are you stating that when there're functional dependencies between components, we should somehow ignore them when incorporating them into a larger piece? say, the kernel…
you conveniently forgot to mention the fundamental difference: the upstream kernel isn't developed for free whereas our code has always been. changes the equation quite a bit, doesn't it?
> Sorry, I assumed that 80% and 86% were close enough that a reasonable reader would be able > to see that I had mis-remembered the second significant figure for statistics I heard a while ago. vs. >>and the source of…
> Sorry, it's 86% and 14% in Linux 4.11. It's literally in the link I posted. you first quoted 80% and chided me for not reading the article linked to because it supposedly implied/had it in there. now you're moving the…
> 1000 small commits can add up to 100 small+simple components vs. > Commits might be patches, but they're sure not components. make up your mind, are components (whatever that means for you) composed of commits or not?…
and the source of those numbers is...? > As for grsecurity, 100% of the core grsecurity team (that work at "Open Source Security") are paid for their work. that's 100% false. both spender and me are developing our code…
careful there, the author line doesn't imply authorship (if it does, the upstream kernel is already violating our copyrights).
i don't quite get what you're arguing now... are you stating that when there're functional dependencies between components, we should somehow ignore them when incorporating them into a larger piece? say, the kernel…
you conveniently forgot to mention the fundamental difference: the upstream kernel isn't developed for free whereas our code has always been. changes the equation quite a bit, doesn't it?