linux-kernel - Re: Linux 2.6.25-rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.00.0804012005030.14670@woody.linux-foundation.org>
Date:	Tue, 1 Apr 2008 20:09:01 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.25-rc8

On Tue, 1 Apr 2008, Linus Torvalds wrote:
> 
> And I think that's how we all work (and how we _should_ work), but 
> sometimes people get so used to the fact that some people are fairly 
> tightly associated with certain code that they think it's about the 
> subsystem, not about the person.

Btw - don't get me wrong - we clearly do try to (and should) make merges 
easy, and it's why the kernel source code is generally pretty modular and 
we try to keep things as independent as possible. I'm not at all arguing 
against that.

I'm just trying to explain that at least personally, I just don't see that 
"modularity" and maintainership as a _primary_ issue. The primary issue is 
just the interpersonal trust people build up over time. The modularity and 
trying to keep borders is about practical concerns, and it's important 
too. But it is still secondary, I think. 

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/