[16:20] <smoser> is it declared / decided what major.minor wily will be ?
[16:22] <rtg> smoser, likely 4.2
[16:23] <rtg> 99% sure
[16:23] <smoser> rtg, thank you. 
[16:25] <smoser> rtg, silly related qestion
[16:25] <smoser> uname will show 4.2.0 ?
[16:26] <smoser> is .0 basically always now ? /me remembers this sort of
[16:26] <rtg> smoser, yup
[16:27] <rtg> smoser, /proc/version_signature shows the stable release version, e.g., 3.13.11-ckt20
[16:29] <infinity> smoser: To be fair, it's always been like this.  As in, our uname never showed patchlevel.
[16:30] <infinity> smoser: It's just that it got a bit wonky when upstream switched from 3-part (plus pl) to 2-part (plus pl), but downstreams were scared to death (rightly so) of userspace exploding with a 2-part uname, so we tacked a fake .0 to the end of it. :P
[16:30] <smoser> that wasn't really what i was asking about.
[16:30] <smoser> more the change from 2.6.18 where major.minor.micro meant one thing to 3.19 where micro essentially is gone.
[16:31] <infinity> smoser: It's actually minor that's gone from that scheme.
[16:31] <infinity> If one wants to be a pedant.
[16:32] <infinity> But yeah, our workaround is confusing.
[16:33] <infinity> And probably worth revisiting some day, but I don't think anyone digs the task of "test all userspace software ever" to see if we can get away with just reporting "4.2".