On Tue, Apr 29, 2008 at 06:47:27PM +0400, Kir Kolyshkin wrote: > As for mainstream integration, I can say OpenVZ is committed to merging > "containers" functionality to mainstream. I have just checked the number > of changesets submitted by OpenVZ and Linux-VServer guys, using > up-to-date Linus' kernel git tree. For the last 365 days (i.e. a year) > there were 818 changesets from OpenVZ guys and only 14 patches from > VServer guys. These numbers could be wrong (maybe I'm missing someone) > but not totally wrong.
indeed the openvz upstream merge record is fun to watch :) IMHO the coding style of vserver is not up to upstream merge quality. even if compared to xen we are quite happy about its etch bug count. > Also, IMHO the document > http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines is not > applicable to this case because it describes patches that are [not] > welcome to "standard" Debian kernel, while OpenVZ, Linux-VServer, Xen > etc. provide "flavored" kernels. In other words, these all are special > kernels with special use cases. So, either this policy is not > applicable, or linux-image-vserver and linux-image-xen are all not > conforming to the policy. sure, it is for random_unsolcited_oot.patch. > As for 2.6.26, OpenVZ team plans to start porting to that kernel as soon > as 2.6.26-rc1 is released. great, please post git tree once it is public, so that we can integrate the flavour for upcoming 2.6.26 Lenny release. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
