mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: Gregory Boyce <gboyce@badbelly.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel releases for security updates
Date: Fri, 14 Jan 2005 09:01:58 +0100	[thread overview]
Message-ID: <41E77C76.3070204@bio.ifi.lmu.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0501121340560.20156@buddha.badbelly.com>

Gregory Boyce wrote

> Rather than actually putting out point releases for the previously 
> released kernels, why not just create a centralized repository for the 
> security patches?  In a lot of cases security patches can be applied as is 
> to a number of different kernel revisions.  For the ones that cannot, 
> variances of the patches could be posted along with it clearly marked as 
> to which patches apply to which kernels.
> 
> Thoughts?

I guess the new -as tree is more or less achieving what you want. If
Andres gets enough support from other people, it might be possible to
maintain even more than one or two former releases...

[x] Voting for the -as tree to become an official tree on kernel.org :-)

cu,
Frank

-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

  parent reply	other threads:[~2005-01-14  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 19:45 Gregory Boyce
2005-01-13 15:36 ` Alan Cox
2005-01-14  8:01 ` Frank Steiner [this message]
2005-01-15  0:32   ` Alan Cox

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=41E77C76.3070204@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=gboyce@badbelly.com \
    --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

all inboxes | Powered by JetHome®