public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: 2.6.16.x will be a long-living kernel series
Date: Fri, 24 Mar 2006 01:22:25 +0100	[thread overview]
Message-ID: <20060324002225.GP22727@stusta.de> (raw)
In-Reply-To: <1142859823.3114.39.camel@laptopd505.fenrus.org>

On Mon, Mar 20, 2006 at 02:03:42PM +0100, Arjan van de Ven wrote:
> On Mon, 2006-03-20 at 13:12 +0100, Adrian Bunk wrote:
> > On Mon, Mar 20, 2006 at 01:05:22PM +0100, Arjan van de Ven wrote:
> > > On Mon, 2006-03-20 at 13:02 +0100, Adrian Bunk wrote:
> > > > As proposed some time ago [1], I'll continue the 2.6.16.x series after 
> > > > 2.6.17 will be released.
> > > 
> > > 
> > > ehh are you doing this as part of the regular stable effort ? Or in
> > > parallel to that?
> > 
> > This seems to be the point I never manage to communicate correctly...
> > 
> > After 2.6.17 will be released, there will be the last regular 2.6.16.x 
> > kernel by Greg and Chris.
> 
> more like after 2.6.18, since they do 2 releases back nowadays

Unless I've misunderstood it, this isn't completely true.

They would do more releases if there are patches sent for them, but in 
practice there is only one release back really done.

> > I'll continue the 2.6.16.x series _after_ this last regular stable 
> > kernel.
> 
> ok
> 
> btw I don't really agree with your criteria, I would strongly suggest
> that you keep using the "stable" criteria.

Simple patches adding support for aditional hardware might be nice.
For stuff in a flux like SATA updates might be nice.

Time will tell.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-03-24  0:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  6:23 Linux v2.6.16 Linus Torvalds
2006-03-20 12:02 ` 2.6.16.x will be a long-living kernel series Adrian Bunk
2006-03-20 12:05   ` Arjan van de Ven
2006-03-20 12:12     ` Adrian Bunk
2006-03-20 13:03       ` Arjan van de Ven
2006-03-24  0:22         ` Adrian Bunk [this message]
2006-03-20 19:22       ` Jan Engelhardt
2006-03-20 17:19 ` Linux v2.6.16 Joe Korty
2006-03-20 19:04   ` Jeff Garzik
2006-03-20 19:25     ` Jan Engelhardt
2006-03-20 19:32       ` Joe Korty
2006-03-20 19:33       ` Linus Torvalds
2006-03-20 21:05         ` Andreas Schwab
2006-03-20 22:52         ` Matthias Andree
2006-03-22  5:22 ` Peter Williams
2006-03-22  6:31   ` Ashok Raj
2006-03-22 13:08     ` Ashok Raj
2006-03-22 13:25       ` Michal Piotrowski
2006-03-22 17:39       ` Rafael J. Wysocki
2006-03-22 17:54         ` Ashok Raj
2006-03-22 18:11           ` Rafael J. Wysocki
2006-03-22 18:27             ` Ashok Raj
2006-03-22 20:40               ` Rafael J. Wysocki
2006-03-22 21:00                 ` Ashok Raj
2006-03-22 21:36                   ` Rafael J. Wysocki
2006-03-22 22:27     ` Peter Williams
2006-03-28 16:39 ` Linux v2.6.16(.1) - compile failure Athanasius
2006-03-31 17:09   ` 'make oldconfig' sub-optimal 2.6.15 -> 2.6.16(.1) (was Re: Linux v2.6.16(.1) - compile failure) Athanasius
2006-04-01  9:18     ` netfilter: IP_NF_CONNTRACK_NETLINK=y, IP_NF_NAT=m compile error 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=20060324002225.GP22727@stusta.de \
    --to=bunk@stusta.de \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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