Hi Daniel, I've refreshed github.com/hallyn/lxc from your upstream tree, gone back through our current ubuntu lxc package, and pushed all the patches from debian and ubuntu which seemed appropriate. The result builds and passes my containers tests (at lp:~serge-hallyn/+junk/lxc-test). Most of these have been sent to lxc-devel before for comments but either not been reviewed, or simply not yet been pulled in. Currently there are 47 patches on top of upstream.
branch upstream.1 is current sf.net lxc git head, while upstream.1.withpatches, the default tree, is the one with patches applied. Ignore the master branch. When sf.net lxc git head is updated, I'll pull that in as upstream.2, etc. Every time we add an upstream-appropriate patch to our package, I'll port it and add it to this tree. If it isn't going to be too annoying, I'd like to add a post-commit hook to email lxc-devel. Obviously I'll disable the hook when causing a lot of noise (i.e. rebasing). -serge ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
