2.6.11-mm4 and 2.6.11.4

2.6.11-mm4 and 2.6.11.4

[Patrick McFarland]

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

I've been running -mm for about a year now, and the whole thing with 2.6.11.x 
releases coming out quite often is a little confusing. Does 2.6.11-mm4 still 
apply to 2.6.11 (no bloody 1, 2, 3, or 4), and if so, what does -mm4 contain 
from the .x versions (ie, does -mm4 contain the updates from 2.6.11.3 or 4 as 
well?)

-- 
Patrick "Diablo-D3" McFarland || pmcfarland@downeast.net
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd 
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.11-mm4 and 2.6.11.4

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Wed, 16 Mar 2005 12:57:15 EST, Patrick McFarland said:

> I've been running -mm for about a year now, and the whole thing with 2.6.11.x
> releases coming out quite often is a little confusing. Does 2.6.11-mm4 still
> apply to 2.6.11 (no bloody 1, 2, 3, or 4), and if so, what does -mm4 contain
> from the .x versions (ie, does -mm4 contain the updates from 2.6.11.3 or 4 as
> well?)

The -mm patches apply on top of a clean 2.6.11.

They *should* contain all the 2.6.11.4 fixes, because Andrew includes the
bk-linus.patch in -mm, and the 2.6.x.y policy is that the patch (or a variant
thereof) already be in upstream.  So Linus's tree has to have it in it, so
the -mm tree should have it.

If you find something that's in 2.6.x.y that *isn't* in a subsequently released
-mm, I suggest you contact Greg, Linus, and Andrew, as it means we've collectively
borked something...


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]