Skip to contentSkip to conversation

Stable 2.6.x.y kernel series...

DISCUSSION Nick Craig-Wood 3 participants 3 messages Jun 7, 2005 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 9 lines · you
Quoted 3 lines · Jeff Garzik

Just wanted to say in public that I think the stable 2.6.x.y kernel series is working out quite well. Kudos to the [email protected] team for a job well done.

Ditto, and its been conservative enough that not only does it stay pretty stable (one partition slip-up so far is very good indeed) its small enough that most of the add on patches people use aren't breaking against it either.

Hearty agreement from me.

The next hurdle for 2.6.11-stable is to make sure that everything that went into it goes into 2.6.12. Is there a procedure for that?

Signature · 1 line
Nick Craig-Wood <[email protected]> -- http://www.craig-wood.com/nick
#3 lore raw

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

Quoted 4 lines · Nick Craig-Wood

Hearty agreement from me.

The next hurdle for 2.6.11-stable is to make sure that everything that went into it goes into 2.6.12. Is there a procedure for that?

Other way around. In order to be accepted into -stable, it needs to already have been accepted into mainline. More information at
http://kerneltrap.org/node/4827/54751

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCpbpmaI0dwg4A47wRAsTSAKCiDtUqKOdr43/lqaBA4zdijGZUygCg3Atb gSmK6WjZQC3jRLbFiqRD6Wk=
=mtKE
-----END PGP SIGNATURE-----

#4 lore raw
Quoted 7 lines · Frank Sorenson

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

Quoted 2 lines · Nick Craig-Wood

Hearty agreement from me.

Quoted 7 lines
Quoted 2 lines

The next hurdle for 2.6.11-stable is to make sure that everything that went into it goes into 2.6.12. Is there a procedure for that?

Other way around. In order to be accepted into -stable, it needs to already have been accepted into mainline. More information at
http://kerneltrap.org/node/4827/54751

It's more complex than that, because -stable allows simple fixes while a complex fix or even total rethink may be in mainline. I'm personally happy with that, although I don't know if it has actually happened.

Signature · 3 lines
   -bill davidsen ([email protected])
"The secret to procrastination is to put things off until the
 last possible moment - but no longer"  -me