Hi BenSorry. My mistake. I looked only at the stable release, not the stable-security release. If I look into the correct one, yes then it is quite obvious.
However I have one additional question as I do not know the process you work with in the kernel team fully. When you update to a newer version of the kernel package, how do you handle openvz in that case? I assume you use the same kernel patch as before, but how do that differ from this case. Or do you mean that the one I referred to was to some other track than the openvz track? In that case, I'm sorry, I did not understand that.
Best regards, / /Ola Quoting "Ben Hutchings" <ben@decadent.org.uk>:
On Mon, 2011-06-20 at 15:00 +0200, Ola Lundqvist wrote:Hi Maks and Kir Kir: Some updated statement from Maks. Maks: I think one reason for not updating is that the version in Debian stable is usually not updated. So it is hard to tell what revision the Debian kernel team is regarding stable updates.[...] It is very easy: you look at the changelog. If you don't want to get the whole package then see: <http://anonscm.debian.org/viewvc/kernel/dists/squeeze/linux-2.6/debian/changelog?revision=HEAD&view=markup> Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson
-- --- Inguza Technology AB --- MSc in Information Technology ---- / ola@inguza.com Annebergsslingan 37 \ | opal@debian.org 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---------------------------------------------------------------