From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
David Miller <davem@davemloft.net>, Jeff Garzik <jeff@garzik.org>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] final SCSI pieces for the merge window
Date: Wed, 24 Oct 2007 12:09:14 -0700 [thread overview]
Message-ID: <20071024120914.180682a6.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0710240818320.30120@woody.linux-foundation.org>
On Wed, 24 Oct 2007 08:35:21 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, 24 Oct 2007, James Bottomley wrote:
> >
> > OK, so it's no secret that I'm the last of the subsystem maintainers
> > whose day job isn't working on the linux kernel. If you want a full
> > time person, who did you have in mind?
>
> Quite frankly, at least for me personally, what I would rather have (in
> general: this is really not at all SCSI-specific in any way, shape, or
> form, and not directed at James!) is a less rigid maintainership
> structure.
>
> Let's face it, we are *all* likely to be overworked at different times,
> and even when not overworked, it's just the fact that people need to take
> a breather etc. And there is seldom - if ever - a very strong argument for
> having one person per subsystem.
Am OK with all of that, but with a rider. It would make my life even more
miserable if there was a (say) git-scsi-tweedledee and a
git-scsi-tweedledum. We already have too much out-of-scope code turning up
in the git trees and having two trees explicitly modifying the same
subsystem would hurt. It's also bad from an engineering POV: there's a
decent chance that when combined, they just won't work.
So Tweedledee and Tweedledum should both commit to the same tree, please.
next prev parent reply other threads:[~2007-10-24 19:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 20:58 [GIT PATCH] final SCSI pieces for the merge window James Bottomley
2007-10-23 21:09 ` Jeff Garzik
2007-10-23 21:20 ` James Bottomley
2007-10-23 22:06 ` Jeff Garzik
2007-10-23 22:36 ` David Miller
2007-10-24 13:28 ` James Bottomley
2007-10-24 14:27 ` Matthew Wilcox
2007-10-30 13:00 ` Denys Vlasenko
2007-10-24 15:14 ` Andrew Morton
2007-10-24 15:35 ` Linus Torvalds
2007-10-24 19:09 ` Andrew Morton [this message]
2007-10-24 9:28 ` Douglas Gilbert
2007-10-24 14:32 ` Jeff Garzik
2007-10-24 13:24 ` James Bottomley
2007-10-24 14:30 ` Jeff Garzik
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=20071024120914.180682a6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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