mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.25-rc8
Date: Tue, 1 Apr 2008 20:09:01 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.00.0804012005030.14670@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0804011948010.14670@woody.linux-foundation.org>



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

  reply	other threads:[~2008-04-02  3:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 20:08 Linus Torvalds
2008-04-01 21:42 ` Paul Mackerras
2008-04-02 14:50   ` Linus Torvalds
2008-04-02 18:54     ` Adrian Bunk
2008-04-03  4:08     ` Paul Mackerras
2008-04-03 12:55       ` Josh Boyer
2008-04-03 18:18         ` Sam Ravnborg
2008-04-02  0:23 ` Stephen Rothwell
2008-04-02  3:03   ` Linus Torvalds
2008-04-02  3:09     ` Linus Torvalds [this message]
2008-04-02 18:57     ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.00.0804012005030.14670@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®