[arch-general] kernel26 in [current] cries for love when new kernel version hits [testing]

[Denis A. Altoé Falqueto]

On Tue, Dec 15, 2009 at 7:58 AM, Emmanuel Benisty <benisty.e at gmail.com> wrote:
> yes, that would solve the problem. but that's not the way the kernel
> update process is designed in Arch. also there are still some blockers
> ATM (lirc for example)

And that is why the .32 kernel is not in [core] yet. As I understand
it, the kernel packaging process shouldn't take long, but sometimes
bugs pop in and they don't always have a solution quick enough. In
this case, .31.8 was released by kernel.org before .32 was stable in
Arch. But it's just an exception, not the rule. I've seen kernels
being released in [core] fast enough.

-- 
A: Because it obfuscates the reading.
Q: Why is top posting so bad?

-------------------------------------------
Denis A. Altoe Falqueto
-------------------------------------------