public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo <paoloc@gmail.com>
To: greg@kroah.com
Cc: chrisw@osdl.org, torvalds@osdl.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.11.1
Date: Fri, 04 Mar 2005 20:28:58 +0100	[thread overview]
Message-ID: <4228B6FA.6040606@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| 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.

First of all, congratulation.
I really think this will be a great improvement to the development process.

I couldn't agree more with this decision, it's really what I suggested a
few months ago:
http://marc.theaimsgroup.com/?l=linux-kernel&m=109882220123966&w=2

Out of curiosity, are you going to include the -as branch ?

		Paolo


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCKLb6xcZDms2c3jQRAkmBAJ9fNXkoo+ATm2wezsRyQzrRxh6siACdFzVo
0cllOTLr40ALnK2S3VJENa0=
=jWOp
-----END PGP SIGNATURE-----

             reply	other threads:[~2005-03-04 19:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 19:28 Paolo [this message]
2005-03-04 19:55 ` Linux 2.6.11.1 Greg KH
2005-03-04 20:01   ` Paolo
2005-03-04 20:00 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
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
2005-03-04 17:53 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

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=4228B6FA.6040606@gmail.com \
    --to=paoloc@gmail.com \
    --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