From: Andrea Arcangeli <andrea@suse.de>
To: Greg KH <greg@kroah.com>
Cc: Adrian Bunk <bunk@stusta.de>, Josh Boyer <jwboyer@gmail.com>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: Adrian Bunk is now taking over the 2.6.16-stable branch
Date: Mon, 21 Aug 2006 00:30:46 +0200 [thread overview]
Message-ID: <20060820223046.GB10011@opteron.random> (raw)
In-Reply-To: <20060806045234.GA28849@kroah.com>
On Sat, Aug 05, 2006 at 09:52:34PM -0700, Greg KH wrote:
> Greg didn't "elect" anyone, Adrian volunteered to maintain something
> that had been dropped by the -stable developers and no one else was
> going to maintain.
Did you ever call for a maintainer list of volunteers?
To me an official 2.6.16-stable in the hands of the only guy who
proposed himself as maintainer, sounds worse than no stable tree at
all. People won't know anymore if to run Greg's 2.6.18-stable or
2.6.16-stable.
If a 2.6-real-stable tree has to happen because 2.6-stable is not
really stable/trustable enough, then give it up with your
2.6.18-stable and start doing 2.7 and leave 2.6 in the hands of
somebody else.
An official kernel needs a critical mass to have a value, it's simply
a wasted effort to open yet another official tree that will actually
fragment the "production" userbase even more.
If 2.6.18-stable is sustainable with the current model, with the
distro folks being the only ones forking off a real-stable tree, then
you should drop 2.6.16-stable. If instead it's 2.6.18-stable that is
not good enough for production usage and people really needs
2.6.16-stable, you should open 2.7, and not fragment the userbase like
this.
I think it would be great to have the users choosing their preferred
maintainer to end the era of maintainers being decided by other
maintainers like you actually did. A simple website on kernel.org can
achieve it, where users can registers for voting and the maintainers
willing to maintain 2.6-stable can registers themself too. That's at
least less random than the current status if what you said above is
true and if 2.6.16-stable is meant to reach any critical mass.
next prev parent reply other threads:[~2006-08-20 22:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 20:49 Adrian Bunk is now taking over the 2.6.16-stable branch Greg KH
2006-08-04 2:43 ` Josh Boyer
2006-08-04 6:26 ` Jan Engelhardt
2006-08-04 23:00 ` Adrian Bunk
2006-08-06 0:46 ` Andrea Arcangeli
2006-08-06 4:52 ` Greg KH
2006-08-20 22:30 ` Andrea Arcangeli [this message]
2006-08-20 22:51 ` Sean
2006-08-20 22:51 ` Sean
2006-08-20 23:15 ` Andrea Arcangeli
2006-08-20 23:38 ` Adrian Bunk
2006-08-21 0:05 ` Willy Tarreau
2006-08-21 13:33 ` Andrea Arcangeli
2006-08-20 23:05 ` Alan Cox
2006-08-20 23:17 ` Andrea Arcangeli
2006-08-21 6:21 ` David Miller
2006-08-21 9:35 ` Andrea Arcangeli
2006-08-22 7:27 ` Matthias Andree
2006-08-24 13:00 ` Pavel Machek
2006-08-06 6:17 ` Willy Tarreau
2006-08-07 12:40 ` Pavel Machek
2006-08-07 16:53 ` [stable] " Greg KH
2006-08-07 17:59 ` Adrian Bunk
2006-08-07 23:30 ` Pavel Machek
2006-08-08 19:55 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 21:45 Chuck Ebbert
2006-08-09 22:00 ` Adrian Bunk
2006-08-09 22:18 ` Greg KH
2006-08-09 22:45 ` Adrian Bunk
2006-08-09 22:53 ` Greg KH
2006-08-09 23:05 ` Chris Wright
2006-08-09 23:20 ` Rene Scharfe
2006-08-10 11:57 ` Stefan Richter
2006-08-12 16:24 ` 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=20060820223046.GB10011@opteron.random \
--to=andrea@suse.de \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.