[Ovirt-devel] [patch] Even Better Exceptions For ruby-libvirt bindings

[Mohammed Morsi]

Mohammed Morsi wrote:
> Mohammed Morsi wrote:
>> I figured out how to add extra information to the exceptions, so from 
>> here on out we should be able to inform the client of whatever it 
>> needs to determine if it should continue processing. Right now, 
>> besides the standard message that ruby exceptions expect, the 
>> invoker's  method_name" (previously just printed out) and 
>> "vir_connect_ptr" are added as attributes to the base ruby-libvirt 
>> exception. Enjoy!
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Ovirt-devel mailing list
>> Ovirt-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/ovirt-devel
> My mistake, I ran "diff" manually, instead of "hg diff", attached is 
> the corrected patch
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ovirt-devel mailing list
> Ovirt-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/ovirt-devel

Oy, let me try this one more time (last time I promise ;-) ). Seems like 
there was a change made that I didn't pull the latest version of the 
code, and thus the "libvirt_dom_pin_vcpu" method is showing up in my 
patch (I'm pretty new to mercurial). Attached is the final version.






-------------- next part --------------
A non-text attachment was scrubbed...
Name: _libvirt.c.patch
Type: text/x-patch
Size: 21501 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20080331/af8432b4/attachment.bin>