From: "L. A. Walsh" <lkml@tlinx.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, chrisw@osdl.org, torvalds@osdl.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.11.1
Date: Sat, 05 Mar 2005 10:32:55 -0800 [thread overview]
Message-ID: <4229FB57.70309@tlinx.org> (raw)
In-Reply-To: <20050304175302.GA29289@kroah.com>
Many, many thanks...it's a great idea and seems to go well
with Linus's idea of making even releases "hyper-stable".
This is exactly what I was looking for in
(http://article.gmane.org/gmane.linux.kernel/268836)
Sorry some of you feel like "suckers"...but you're _not_.
You're heroes -- doing the hard sh*t that most programmers
don't want to be bothered with. I salute you!
Linda W.
Greg KH wrote:
>For those of you who haven't waded through the huge "RFD: Kernel release
>numbering" thread on lkml to realize that we are now going to start
>putting out 2.6.x.y releases, here's the summary:
>
> A few of us $suckers will be trying to maintain a 2.6.x.y set of
> releases that happen after 2.6.x is released. It will contain
> only a set of bugfixes and security fixes that meet a strict set
> of guidelines, as defined by Linus at:
> http://article.gmane.org/gmane.linux.kernel/283396
>
>Chris Wright and I are going to start working on doing this work, we
>will have a <SOME_ALIAS>@kernel.org to post these types of bug fixes to,
>and a set of people we bounce the patches off of to test for "smells
>good" validation. We will also have a bk-commits type mailing list for
>those who want to watch the patches flow in, and a bk tree from which
>changsets can be pulled from.
>
>Chris and I will be hashing all of the details out next Tuesday, and
>hopefully all the infrastructure will be in place soon. When that
>happens, we will post the full details on how all of this is going to
>work. In the meantime, feel free to CC: me and Chris on patches that
>everyone thinks should go into the 2.6.11.y releases.
>
>But right now, Chris is on a plane, and we don't have the email alias
>set up, or the proper permissions set up on kernel.org to push changes
>into the v2.6 directory, but we have a few bugs that are needing to be
>fixed in the 2.6.11 release. And since our mantra is, "release early
>and often", here's the first release.
>
>---------------
>
>I've released the 2.6.11.1 patch:
> kernel.org/pub/linux/kernel/people/gregkh/v2.6.11/patch-2.6.11.1.gz
>
>With a detailed changelog at:
> kernel.org/pub/linux/kernel/people/gregkh/v2.6.11/ChangeLog-2.6.11.1
>
>A bitkeeper tree for the 2.6.11.y releases can be found at:
> bk://linux-release.bkbits.net/linux-2.6.11
>
>The diffstat and short summary of the fixes are below.
>
>I'll also be replying to this message with a copy of the patch itself,
>as it is small enough to do so.
>
>thanks,
>
>greg k-h
>
>-------
>
> Makefile | 2 +-
> drivers/input/serio/i8042-x86ia64io.h | 6 +++---
> drivers/md/raid6altivec.uc | 4 ++++
> 3 files changed, 8 insertions(+), 4 deletions(-)
>
>
>Summary of changes from v2.6.11 to v2.6.11.1
>============================================
>
>Dmitry Torokhov:
> o Fix keyboards for Dell machines
>
>Greg Kroah-Hartman:
> o Linux 2.6.11.1
>
>Olof Johansson:
> o Fix for trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
>
>Rene Rebe:
> o trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2005-03-05 18:38 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:53 Linux 2.6.11.1 Greg KH
2005-03-04 17:53 ` Greg KH
2005-03-04 20:34 ` Ian Pilcher
2005-03-04 22:29 ` Greg KH
2005-03-04 20:44 ` Andrew Morton
2005-03-04 20:58 ` Greg KH
2005-03-04 21:15 ` Andrew Morton
2005-03-04 21:43 ` Greg KH
2005-03-04 21:54 ` Andrew Morton
2005-03-04 22:08 ` Greg KH
2005-03-04 21:53 ` Linus Torvalds
2005-03-04 21:59 ` Andrew Morton
2005-03-04 22:05 ` Greg KH
2005-03-04 22:36 ` Andrew Morton
2005-03-05 0:06 ` Greg KH
2005-03-05 0:28 ` Linus Torvalds
2005-03-05 7:53 ` Dave Jones
2005-03-06 5:05 ` Greg KH
2005-03-05 1:37 ` Jeff Garzik
2005-03-06 5:03 ` Greg KH
2005-03-05 9:51 ` Russell King
2005-03-05 17:19 ` Jeff Garzik
2005-03-05 17:40 ` Linus Torvalds
2005-03-05 17:46 ` Russell King
2005-03-05 21:17 ` Linus Torvalds
2005-03-05 21:49 ` Gene Heskett
2005-03-05 22:06 ` Lee Revell
2005-03-05 23:26 ` Gene Heskett
2005-03-07 17:18 ` Alan Cox
2005-03-08 20:16 ` Lee Revell
2005-03-05 17:50 ` Jeff Garzik
2005-03-05 18:22 ` Randy.Dunlap
2005-03-05 0:24 ` Jeff Garzik
2005-03-04 21:15 ` Trond Myklebust
2005-03-04 21:33 ` Jeff Garzik
2005-03-04 21:51 ` Andrew Morton
2005-03-04 21:58 ` Jeff Garzik
2005-03-05 7:11 ` James Bourne
2005-03-08 22:07 ` Bill Davidsen
2005-03-08 22:41 ` Chris Wright
2005-03-04 21:50 ` Dave Jones
2005-03-04 23:35 ` Andries Brouwer
2005-03-04 20:48 ` Steven Rostedt
2005-03-04 20:53 ` Greg KH
2005-03-04 21:02 ` Steven Rostedt
2005-03-05 18:32 ` L. A. Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 19:28 Paolo
2005-03-04 19:55 ` Greg KH
2005-03-04 20:01 ` Paolo
2005-03-04 20:00 ` Jeff Garzik
2005-03-05 6:16 Shawn Starr
2005-03-06 5:06 ` Greg KH
2005-03-07 4:01 ` Shawn Starr
2005-03-07 3:58 ` Randy.Dunlap
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=4229FB57.70309@tlinx.org \
--to=lkml@tlinx.org \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.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