public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrea Arcangeli <andrea@suse.de>
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: Sat, 5 Aug 2006 21:52:34 -0700	[thread overview]
Message-ID: <20060806045234.GA28849@kroah.com> (raw)
In-Reply-To: <20060806004634.GB6455@opteron.random>

On Sun, Aug 06, 2006 at 02:46:34AM +0200, Andrea Arcangeli wrote:
> On Sat, Aug 05, 2006 at 01:00:17AM +0200, Adrian Bunk wrote:
> > On Thu, Aug 03, 2006 at 09:43:06PM -0500, Josh Boyer wrote:
> > > On 8/3/06, Greg KH <greg@kroah.com> wrote:
> > > >This is just a notice to everyone that Adrian is going to now be taking
> > > >over the 2.6.16-stable kernel branch, for him to maintain for as long as
> > > >he wants to.
> > > 
> > > Adrian, could you provide a bit of rationale as to why you want to do
> > > this?  I'm just curious.
> > 
> > A long-term maintained stable series was missing in the current 
> > development model.
> > 
> > The 2.6 series itself is theoretically a stable series, but the amount 
> > of regressions is too big for some users.
> 
> Greg is electing new official maintainers

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.

> , but Greg is doing other
> weird things as well:
> 
>        http://www.cpushare.com/blog/andrea/article/42/

I'm only repeating what a whole lot of lawyers told me, nothing else.

thanks,

greg k-h

  reply	other threads:[~2006-08-06  4:56 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 [this message]
2006-08-20 22:30         ` 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
     [not found]           ` <20060820185123.e84fafaf.seanlkml@sympatico.ca>
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-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=20060806045234.GA28849@kroah.com \
    --to=greg@kroah.com \
    --cc=andrea@suse.de \
    --cc=bunk@stusta.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox