From: Daniel Drake <dsd@gentoo.org>
To: Andres Salomon <dilinger@voxel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-as1
Date: Thu, 13 Jan 2005 20:11:36 +0000 [thread overview]
Message-ID: <41E6D5F8.2040901@gentoo.org> (raw)
In-Reply-To: <1105605448.7316.13.camel@localhost>
Hi,
Andres Salomon wrote:
> 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.
After all of the recent discussion it's nice to see someone step up and do this :)
Thanks a lot, I'm sure I will find it useful when producing gentoo's kernel
packages..
Just one suggestion- maybe could you distinguish security patches from
bugfixes? I.e. prepend or append the security patches with "sec" or something?
Thanks,
Daniel
next prev parent reply other threads:[~2005-01-13 18:13 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 ` 2.6.10-as1 Andres Salomon
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 ` Daniel Drake [this message]
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=41E6D5F8.2040901@gentoo.org \
--to=dsd@gentoo.org \
--cc=dilinger@voxel.net \
--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