From: Andres Salomon <dilinger@voxel.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10-as1
Date: Thu, 13 Jan 2005 03:37:28 -0500 [thread overview]
Message-ID: <1105605448.7316.13.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
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.
This first release should have been done last week, but the various
security advisories kept me pretty busy. It includes various iptables
and nfs fixes, the various security fixes announced over the past two
weeks (including the latest, CAN-2005-0001), and misc. others. My hope
is that people find this useful, so less work is duplicated by
distribution packagers. Debian kernels are basically a combination of
this tree, as well as debian-specific patches and more experimental
stuff.
The kernel patches can be grabbed from here:
http://www.acm.rpi.edu/~dilinger/patches/2.6.10/as1/
02e412361955fa80c0ea3a5a59a37c36 ChangeLog
0a75d0e8922491fb2540b3c6178dfd58 linux-2.6.10-as1.tar.gz
540effd229ea72dad4bd274bba40fb94 patch-2.6.10-as1.gz
patch-2.6.10-as1.gz is a patch against vanilla 2.6.10.
linux-2.6.10-as1.tar.gz are the patches, individually broken out.
Patches pulled from bitkeeper include their comment headers.
As mentioned, this should've been released last week; as such, it's
about a week behind bitkeeper. I shall go through the remaining 600 or
so changesets within the next few days, and release -as2.
--
Andres Salomon <dilinger@voxel.net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-13 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 8:37 Andres Salomon [this message]
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 ` 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=1105605448.7316.13.camel@localhost \
--to=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