- Original Message -
> From: "Mark Wu"
> To: "Igor Lvovsky"
> Cc: "Antoni Segura Puimedon" ,
> vdsm-devel@lists.fedorahosted.org, "Dan Kenigsberg"
>
> Sent: Wednesday, December 12, 2012 8:22:29 AM
> Subject: Re: [vdsm] Fwd: Bonding, bridges and ifcfg
>
> On 12/12/2012 03:13 PM, Igor
Hi,
When there is the attempt to enhance/change the current API, I would ask
you to consider to think also about the vdsClient use case.
I haven't read anything regarding that so far and therefore I just want
you to think about it as well.
My expectation is that the vdsClient will continue to
- Original Message -
> From: "Dan Kenigsberg"
> To: vdsm-devel@lists.fedorahosted.org
> Cc: "Federico Simoncelli" , "Mike Burns"
>
> Sent: Tuesday, December 11, 2012 8:24:49 PM
> Subject: v4.10.3 tagged
>
> I've just tagged v4.10.3 of vdsm. It has several interesting changes
> since the
- Original Message -
> From: "Antoni Segura Puimedon"
> To: "Mark Wu"
> Cc: vdsm-devel@lists.fedorahosted.org, "Dan Kenigsberg" ,
> "Igor Lvovsky"
> Sent: Wednesday, December 12, 2012 2:18:07 PM
> Subject: Re: [vdsm] Fwd: Bonding, bridges and ifcfg
>
>
>
> - Original Message --
On Wed, Dec 12, 2012 at 02:01:31PM +0100, Vinzenz Feenstra wrote:
> Hi,
>
> When there is the attempt to enhance/change the current API, I would
> ask you to consider to think also about the vdsClient use case.
> I haven't read anything regarding that so far and therefore I just
> want you to thin
Hi Dan,
Recently you merged a patch which will generate api documentation from the
schema at build time. This has an intended side-effect of validating the
schema. Thanks for merging it. It has already pointed out three schema errors
and the Jenkins build jobs are noting the problem [1]. Pleas
