On Mon, Sep 15, 2014 at 12:35 PM, hasufell wrote:
> Jauhien Piatlicki:
>> Hi,
>>
>> On 09/15/2014 01:37 AM, Kent Fredric wrote:
>>> On 15 September 2014 11:25, hasufell wrote:
>>>
Robin said
> The Git commit-signing design explicitly signs the entire commit,
including blob contents,
>should not cause any issues (provided compilation goes through).
There are few packages which compile fine but break something (I remember
some x11-library from bugzilla that broke xorg-server), but generally I
agree with you.
One annoying package is 64bit firefox, which can easily eat up to 15GB
This reminds me of: http://imgs.xkcd.com/comics/standards.png
It sure sounds nicely, however I would not want to be the guy who maintains
the whole mess of (often) incompatible patchsets.
Given the fact that some patches lag 1-3 stable versions behind Linuses
tree (grsec used by hardened for exampl
Not really, Linus has his own web of trust and he don't take stuff
from unknown sources, he has his liutennants and every single patch
and change must be reviewed by at least two other maintainers below
Linus.
After all, Linux does not belong to Linus and his branch is by
definition of distributed
