These patches are based on those I sent last week (the public
virInterface*() API definition, the local plumbing, and the RPC glue),
but with suggestions incorporated:
1) MAC address is always used in null-terminated ASCII string
format. This eliminates any potential problems with extra long
On Mon, May 18, 2009 at 04:07:29PM -0400, Laine Stump wrote:
These patches are based on those I sent last week (the public
virInterface*() API definition, the local plumbing, and the RPC glue),
but with suggestions incorporated:
1) MAC address is always used in null-terminated ASCII string
why these mail send to libvir-l...@laine.org?
this breaks all mail filters...:-(
Daniel P. Berrange wrote:
On Mon, May 18, 2009 at 04:07:29PM -0400, Laine Stump wrote:
These patches are based on those I sent last week (the public
virInterface*() API definition, the local plumbing, and the RPC
On Mon, May 18, 2009 at 10:21:50PM +0200, Farkas Levente wrote:
why these mail send to libvir-l...@laine.org?
this breaks all mail filters...:-(
For a reliable filter, you're probably better off hooking onto the
standard List-ID header which mailman guarentees will always be
set correctly for
On 05/18/2009 04:21 PM, Farkas Levente wrote:
why these mail send to libvir-l...@laine.org?
this breaks all mail filters...:-(
Sorry, that was a rushed mistype on my part that I tried to fix by just
bouncing the mail rather than regenerating it; I hadn't considered that
people might be
On Fri, May 08, 2009 at 01:52:22PM -0400, Laine Stump wrote:
These 5 patches contain the public virInterface*() API definition, the
local plumbing, and the RPC glue. The test driver and real driver are
still TBI, but having this in will allow other people to work on related
stuff.
Okay,
These 5 patches contain the public virInterface*() API definition, the
local plumbing, and the RPC glue. The test driver and real driver are
still TBI, but having this in will allow other people to work on related
stuff.
Other things still needed:
python/java bindings
cli commands in virsh
I'm
