public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@voxel.net>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-as1
Date: Thu, 13 Jan 2005 10:26:00 -0500	[thread overview]
Message-ID: <1105629960.9553.4.camel@localhost> (raw)
In-Reply-To: <41E648D4.1050906@bio.ifi.lmu.de>

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

On Thu, 2005-01-13 at 11:09 +0100, Frank Steiner wrote:
> Andres Salomon wrote
> 
> > Hi,
> > 
> > I'm announcing a new kernel tree; -as.  The goal of this tree is to form
> > a stable base for vendors/distributors to use for their kernels.  In
> > order to do this, I intend to include only security fixes and obvious
> > bugfixes, from various sources.  I do not intend to include driver
> > updates, large subsystem fixes, cleanups, and so on.  Basically, this is
> > what I'd want 2.6.10.1 to contain.
> 
> Very nice idea! Not only for distributors! Thanks for doing this!
> Do you plan to maintain -as only for the latest release, i.e., will
> 2.6.10-as still be maintained with security fixes even when 2.6.11-as
> comes up?
> 

My plan is to include security fixes for a kernel or two behind what is
the latest.  Currently, I'm supporting (for Debian) 2.6.8 through
2.6.10.  Of course, normally I wouldn't support 2.6.8 for this long, but
since sarge will (hopefully?) be releasing someday, and this is the
kernel chosen for it, I must continue support.

I do not plan to continue small bugfixes for older kernels too much
longer after a new kernel is released; however, if people were to feed
me patches for older kernels, I'd be more than happy to do releases.


-- 
Andres Salomon <dilinger@voxel.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-01-13 15:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  8:37 2.6.10-as1 Andres Salomon
2005-01-13 10:09 ` 2.6.10-as1 Frank Steiner
2005-01-13 15:26   ` Andres Salomon [this message]
2005-01-13 16:18     ` 2.6.10-as1 Frank Steiner
2005-01-13 16:26 ` 2.6.10-as1 Phil Oester
2005-01-13 20:11 ` 2.6.10-as1 Daniel Drake
2005-01-13 18:48   ` 2.6.10-as1 Felipe Alfaro Solana
2005-01-14  3:15     ` 2.6.10-as1 Andres Salomon
2005-01-13 19:08   ` 2.6.10-as1 Andres Salomon
2005-01-14  8:05 ` 2.6.10-as1 Raphael Zimmerer
2005-01-14 14:20   ` 2.6.10-as1 Andres Salomon
2005-01-14 16:33 ` 2.6.10-as1 Frank Steiner
2005-01-14 23:31   ` 2.6.10-as1 Daniel Drake
2005-01-14 21:26     ` 2.6.10-as1 Andres Salomon
2005-01-15  2:41       ` 2.6.10-as1 Daniel Drake
2005-01-18  6:36         ` 2.6.10-as1 Frank Steiner
2005-01-24 17:10 ` 2.6.10-as1 / 2.4 security-only patchset? Pasi Kärkkäinen
2005-01-24 19:32   ` Marcelo Tosatti

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=1105629960.9553.4.camel@localhost \
    --to=dilinger@voxel.net \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --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