From: Patrick McFarland <unknown@panax.com>
To: Andrew Pimlott <andrew@pimlott.ne.mediaone.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.16-pre1
Date: Sun, 25 Nov 2001 19:56:38 -0500 [thread overview]
Message-ID: <20011125195637.O238@localhost> (raw)
In-Reply-To: <20011125151543.57a1159c.skraw@ithnet.com> <Pine.LNX.4.33.0111251007140.9377-100000@penguin.transmeta.com> <20011125170701.H238@localhost> <20011125192056.A10729@pimlott.ne.mediaone.net>
In-Reply-To: <20011125192056.A10729@pimlott.ne.mediaone.net>
For the 52 and a half time, Im not trying to nock Linus. I think hes possibly the best coder we have. (if not the best, atleast in the top 3) But he isnt the best choice of maintainer. And yeah, he did pretty well with 2.4, but it wasnt as good as it could have been. And also, ive been noticing, alot of people disagree with me on this, that the head developer shouldnt be the head maintainer. But how many projects that are this large can you name? Like, i dunno, xfree? That has questionable maintainability. Gnome? KDE? They are fairing okay, but It could be better. And I like the kernel qa group idea, but where would we get the people to be on it? ac and lt are usually too busy, tho, atleast with ac (in top 3 of coders, best linux maintainer we have ever had) 2.5 would get maintained well so linus can focus on coding like I belive he should be. Im a coder myself, so I know how hard it is to maintain a project when it gets big. (I kinda get bored of it like linus does)
Also, alot of people have been saying that I dont know about the section maintainers, like that dave m guy is a maintainer for the network stuff, im talking more of a kernel wide maintainer. Which brings another point. We have per section maintainers, but no real dedicated development tree kernel wide maintainer.
On 25-Nov-2001, Andrew Pimlott wrote:
> On Sun, Nov 25, 2001 at 05:07:01PM -0500, Patrick McFarland wrote:
> > Then quit being maintainer.
>
> I for one believe that Linus was the best person to lead Linux
> through the 2.4 series stabilization. It was bumpy, but who else
> could have pulled off the rather deep changes that put 2.4 on firmer
> footing? On the down side, he released some kernels with small but
> annoying bugs. A small price, in my estimation. Hardly grounds for
> disqualification.
>
> If this is such a concern for you, form a post-Linus QA group that
> certifies Linus kernels after testing them and applying small
> bug-fixes. Then, you get the benefits of Linus's judgement without
> the brown paper bags. Sounds like a win all around.
>
> If you want to knock Linus[1], I hope you can do better than
> complaining about a few bugs. Demonstrate that Linux would be
> better off long-term if Linus had dropped 2.4 after 2.4.0. I
> strongly doubt you can make that case.
>
> Andrew
>
> [1] Not that it matters in the end, because it's his kernel. But at
> least you should make a respectable argument.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Patrick "Diablo-D3" McFarland || unknown@panax.com
next prev parent reply other threads:[~2001-11-26 0:59 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 18:39 Linux 2.4.16-pre1 Marcelo Tosatti
2001-11-24 18:40 ` Marcelo Tosatti
2001-11-24 20:36 ` Phil Sorber
2001-11-24 19:44 ` Marcelo Tosatti
2001-11-24 21:14 ` Linus Torvalds
2001-11-24 21:32 ` H. Peter Anvin
2001-11-24 22:04 ` François Cami
2001-11-26 0:49 ` Horst von Brand
2001-11-26 0:51 ` H. Peter Anvin
2001-11-26 17:50 ` Alan Cox
2001-11-26 18:08 ` H. Peter Anvin
2001-11-26 0:51 ` David Weinehall
2001-11-26 0:53 ` H. Peter Anvin
2001-11-25 1:56 ` Patrick McFarland
2001-11-25 2:12 ` Patrick McFarland
2001-11-25 2:34 ` war
2001-11-25 2:41 ` Patrick McFarland
2001-11-25 3:05 ` Mohammad A. Haque
2001-11-25 21:55 ` Patrick McFarland
2001-11-26 12:06 ` Martin Persson
2001-11-26 14:26 ` David Lang
2001-11-26 16:55 ` Alan Cox
2001-11-26 16:58 ` Dominik Kubla
2001-11-26 15:38 ` M. Edward (Ed) Borasky
2001-11-26 18:12 ` J Sloan
2001-11-25 4:10 ` J Sloan
2001-11-25 21:58 ` Patrick McFarland
2001-11-25 22:57 ` J Sloan
2001-11-25 23:11 ` Patrick McFarland
2001-11-26 0:26 ` Patrick McFarland
2001-11-26 0:31 ` Patrick McFarland
2001-11-26 0:39 ` CaT
2001-11-25 4:23 ` Victor Yodaiken
2001-11-25 3:04 ` John Alvord
2001-11-26 18:13 ` Alan Cox
2001-11-26 18:09 ` H. Peter Anvin
2001-11-24 20:58 ` Ryan Cumming
2001-11-24 22:21 ` H. Peter Anvin
2001-11-24 22:35 ` kernel.org maintenance Ahmed Masud
2001-11-24 22:56 ` Linux 2.4.16-pre1 Mohammad A. Haque
2001-11-24 21:09 ` Marc A. Ohmann
2001-11-24 19:54 ` Marcelo Tosatti
2001-11-24 21:13 ` Arnaldo Carvalho de Melo
2001-11-24 23:32 ` F.H. Bulthuis
2001-11-24 23:37 ` Rik van Riel
2001-11-24 23:47 ` F.H. Bulthuis
2001-11-25 13:34 ` Dominik Kubla
2001-11-25 14:15 ` Stephan von Krawczynski
2001-11-25 18:07 ` Tobias Ringstrom
2001-11-25 18:17 ` Linus Torvalds
2001-11-25 19:16 ` Stephan von Krawczynski
2001-11-25 22:07 ` Patrick McFarland
2001-11-25 19:27 ` Alex Bligh - linux-kernel
2001-11-25 22:13 ` Arnaldo Carvalho de Melo
2001-11-25 22:18 ` Patrick McFarland
2001-11-25 22:26 ` Arnaldo Carvalho de Melo
2001-11-25 22:31 ` Arnaldo Carvalho de Melo
2001-11-26 1:16 ` Mohammad A. Haque
2001-11-26 1:33 ` Patrick McFarland
2001-11-26 2:45 ` Mohammad A. Haque
2001-11-26 2:50 ` Horst von Brand
2001-11-27 0:47 ` Patrick McFarland
2001-11-27 1:01 ` Rik van Riel
2001-11-27 1:04 ` Patrick McFarland
2001-11-27 1:02 ` Andre Hedrick
2001-11-26 10:44 ` Rik van Riel
2001-11-26 6:57 ` Martin Eriksson
2001-11-25 22:28 ` François Cami
2001-11-25 22:36 ` Patrick McFarland
2001-11-25 22:40 ` Patrick McFarland
2001-11-26 0:20 ` Andrew Pimlott
2001-11-26 0:56 ` Patrick McFarland [this message]
2001-11-26 1:16 ` Phil Oester
2001-12-04 20:28 ` The Doctor What
2001-12-04 20:51 ` Rik van Riel
2001-11-25 23:53 ` [RFC] 2.5/2.6/2.7 transition [was Re: Linux 2.4.16-pre1] Mike Fedyk
2001-11-26 3:58 ` Linus Torvalds
2001-11-26 5:33 ` Mike Fedyk
2001-11-26 10:59 ` Rik van Riel
2001-11-26 14:58 ` jlnance
2001-11-26 18:18 ` H. Peter Anvin
2001-11-26 12:41 ` Horst von Brand
2001-11-26 19:35 ` Andrew Morton
2001-11-26 17:44 ` Rob Landley
2001-11-26 21:08 ` Alan Cox
2001-11-26 21:42 ` Rob Landley
2001-11-26 23:52 ` Rob Landley
2001-11-27 3:40 ` Johan Kullstam
2001-11-26 8:13 ` John Alvord
2001-11-25 14:39 ` Linux 2.4.16-pre1 Florian Weimer
2001-11-25 14:51 ` Russell King
2001-11-25 14:58 ` Florian Weimer
2001-11-25 15:06 ` Alexander Viro
2001-11-25 15:14 ` Bruce Harada
2001-11-25 21:44 ` Teodor Iacob
2001-11-25 21:24 ` Thiago Rondon
2001-11-25 21:51 ` Arnaldo Carvalho de Melo
2001-11-26 17:07 ` vda
2001-11-26 16:36 ` Charles Marslett
2001-11-27 4:30 ` Mike Fedyk
2001-11-27 8:59 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 21:56 Ricardo Galli
2001-11-25 12:09 Fred Bulthuis
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=20011125195637.O238@localhost \
--to=unknown@panax.com \
--cc=andrew@pimlott.ne.mediaone.net \
--cc=linux-kernel@vger.kernel.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