On 07.02.2013 18:46, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
To enable locking to be introduced to the security manager
objects later, turn virSecurityManager into a virObjectLockable
class
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
On 02/19/2013 04:16 AM, Michal Privoznik wrote:
It seems like you squashed in changes made to HACKING in. I believe that
was by mistake. However, if HACKING gets re-generated on my system,
git-diff complains about it.
I've noticed that the version of xsltproc in RHEL 6 and Fedora 17
On 02/07/2013 06:46 PM, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
To enable locking to be introduced to the security manager
objects later, turn virSecurityManager into a virObjectLockable
class
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
On 02/07/2013 10:46 AM, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
To enable locking to be introduced to the security manager
objects later, turn virSecurityManager into a virObjectLockable
class
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
From: Daniel P. Berrange berra...@redhat.com
To enable locking to be introduced to the security manager
objects later, turn virSecurityManager into a virObjectLockable
class
Signed-off-by: Daniel P. Berrange berra...@redhat.com
---
src/lxc/lxc_controller.c| 2 +-
src/lxc/lxc_driver.c
