Skip to contentSkip to conversation

Linux 2.6.11.1

DISCUSSION Paolo 3 participants 4 messages Mar 4, 2005

lore
Share & tools
lore

Paolo

author
#0 lore 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-----

#1 lore raw
Quoted 1 line · Paolo

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

The -as stuff should be built on top of 2.6.11.X.

2.6.11.X should not be "every fix under the sun, until 2.6.12 is released."

Jeff

#2 lore raw
In reply to Paolo
Quoted 1 line · Paolo

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

The whole thing? No, see previous comments about the contents of the -as and -ac "branches" in the big lkml thread.

But if people will forward on bits and pieces of the -as and -ac tree, to us, and the patches meet the critera we have set up, then I do not see any problem with accepting them.

thanks,

gre k-h

author
#3 lore raw

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

Greg KH wrote:

| On Fri, Mar 04, 2005 at 08:28:58PM +0100, Paolo wrote:
|
|>Out of curiosity, are you going to include the -as branch ?
|
|
| The whole thing?  No, see previous comments about the contents of the
| -as and -ac "branches" in the big lkml thread.

Right, the whole -as tree is really too much ;)

| But if people will forward on bits and pieces of the -as and -ac tree,
| to us, and the patches meet the critera we have set up, then I do not
| see any problem with accepting them.

Ok, hopefully that will become reality.

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

iD8DBQFCKL6VxcZDms2c3jQRAkZ4AKDKk8m3OiBJs5j6WnSIm9jGdnuZogCeIzDE QeoyAI0JaQzPjZm4UR2q1Oo=
=7dic
-----END PGP SIGNATURE-----