From: ibuprofin@painkiller.example.tld.invalid   
      
   On Sun, 03 Mar 2013, in the Usenet newsgroup alt.os.linux.mandriva, in article   
   , TJ wrote:   
      
   >Moe Trin wrote:   
      
   >> Minor "head's up".   A new patch in several 3.x kernels:   
      
   >> That got into 3.4.34, 3.7.10 and 3.8.1 this week.   3.0.67 was also   
   >> released at the same time but did not include this patch.   
      
   >Mageia updated the computer that uses the server kernel to 3.4.34   
   >yesterday. But when I looked into it, the new desktop kernel, which is   
   >what both computers with the b43 device use, apparently hadn't hit the   
   >mirrors quite yet.   
      
   I'm sure you understand that there are inevitable delays here.  I'm   
   looking at ftp://ftp.kernel.org/pub/linux/kernel/v3.0/, and I find   
      
        101144024 Feb 28 15:05 linux-3.4.34.tar.gz   
      
   but when I look at the ChangeLog-3.4.34 (dated the same), the first   
   item is the kernel commit, which reads   
      
    commit 048b6fe6dccb105512147eb47accbb1431b4e54b   
    Author: Greg Kroah-Hartman    
    Date:   Thu Feb 28 07:01:22 2013 -0800   
      
       Linux 3.4.34   
      
   or several minutes before the tarball timestamp (which should be UTC).   
   If I grep the ChangeLog for "Feb 2", I find   
      
   [fermi ~]$ zgrep ' Feb 2' /net/james-webb/kernel/ChangeLog-3.4.34.gz |   
    sort -k3   
   Date:   Thu Feb 21 00:09:54 2013 +0000   
   Date:   Thu Feb 21 01:55:50 2013 +0000   
   Date:   Thu Feb 21 12:18:52 2013 +0000   
   Date:   Thu Feb 21 16:41:59 2013 -0800   
   Date:   Thu Feb 21 16:42:01 2013 -0800   
   Date:   Thu Feb 21 16:42:45 2013 -0800   
   Date:   Thu Feb 21 16:44:04 2013 -0800   
   Date:   Thu Feb 21 23:32:27 2013 +0000   
   Date:   Fri Feb 22 16:35:34 2013 -0800   
   Date:   Fri Feb 22 16:35:59 2013 -0800   
   Date:   Fri Feb 22 16:36:01 2013 -0800   
   Date:   Sat Feb 23 00:32:19 2013 +0100   
   Date:   Sat Feb 23 01:13:47 2013 +0000   
   Date:   Thu Feb 28 07:01:22 2013 -0800   
   [fermi ~]$   
      
   so it takes several days from the commits to the release at kernel.org   
   (and 3.4.34 actually has 6 of the 86 commit dates from 2012).  I'm sure   
   it takes more than a day or two for the distributions to discover that   
   a new kernel has been release, look it over and decide whether to adopt   
   it in whole or (as often happens) cherry-pick stuff.  Then they have to   
   do at least some testing to see that it's not going to blow up.  Only   
   then does it get put into the updates distribution channel, and users   
   can access it.  "Rome wasn't built in a day" - nor was Syracuse   ;-)   
      
   >I'm sure it will be there soon. It may be there now, don't have time   
   >to check at the moment.   
      
   As you say, that's what the crack staff are for.  Reading between the   
   lines in the ChangeLog, this doesn't sound like a "critical" update for   
   your systems - more of a "nice to have".   
      
           Old guy   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)