On Tue, Apr 21, 2015 at 06:41:36PM +0200, Michal Privoznik wrote:
On 16.04.2015 16:46, Martin Kletzander wrote:
The first class in this file is going to be an abstract connection class
that holds a per-connection error inside. virConnect will be the first
child class inheriting from this one.
On 16.04.2015 16:46, Martin Kletzander wrote:
> The first class in this file is going to be an abstract connection class
> that holds a per-connection error inside. virConnect will be the first
> child class inheriting from this one.
>
> This is a separate file because virerror.c is going to depe
On Fri, Apr 17, 2015 at 11:16:49AM +0100, Daniel P. Berrange wrote:
On Thu, Apr 16, 2015 at 04:46:37PM +0200, Martin Kletzander wrote:
The first class in this file is going to be an abstract connection class
that holds a per-connection error inside. virConnect will be the first
child class inhe
On Thu, Apr 16, 2015 at 04:46:37PM +0200, Martin Kletzander wrote:
> The first class in this file is going to be an abstract connection class
> that holds a per-connection error inside. virConnect will be the first
> child class inheriting from this one.
>
> This is a separate file because virerr
The first class in this file is going to be an abstract connection class
that holds a per-connection error inside. virConnect will be the first
child class inheriting from this one.
This is a separate file because virerror.c is going to depend on it and
putting it into datatypes along with other
