Skip to contentSkip to conversation

Stable 2.6.x.y kernel series...

DISCUSSION Nick Craig-Wood 2 participants 3 messages Jun 7, 2005 4 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]

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]

#4 lore raw
Quoted 7 lines · Frank Sorenson
Quoted 2 lines · Nick Craig-Wood

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 doesn't actually say that on the above web page. I remember it being discussed, but it isn't on that page (unless I've missed it of course ;-)

It wouldn't always be appropriate either - a -stable patch might disable something which has a huge security hole in, wheras that sort of patch wouldn't get accepted in mainline.

Signature · 1 line
Nick Craig-Wood <[email protected]> -- http://www.craig-wood.com/nick
#5 lore raw
Quoted 9 lines · * Nick Craig-Wood ([email protected]) wrote:
Quoted 7 lines · Frank Sorenson
Quoted 2 lines · Nick Craig-Wood

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

Quoted 7 lines

It doesn't actually say that on the above web page. I remember it being discussed, but it isn't on that page (unless I've missed it of course ;-)

It wouldn't always be appropriate either - a -stable patch might disable something which has a huge security hole in, wheras that sort of patch wouldn't get accepted in mainline.

There's lot of grey areas, those are guidelines for acceptance. And, per your earlier comment, we do push patches to Linus where appropriate. Typically, we prefer to see them upstream, helps add much credibility to the stability of the patch.

#6 lore raw
Quoted 4 lines · Chris Wright

There's lot of grey areas, those are guidelines for acceptance. And, per your earlier comment, we do push patches to Linus where appropriate. Typically, we prefer to see them upstream, helps add much credibility to the stability of the patch.

Good! I'd just hate to see all that hard work go missing when 2.6.12 is released.

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