On Thu, Aug 25, 2011 at 04:28:32PM -0700, Ben Pfaff wrote:
> On Fri, Aug 26, 2011 at 08:25:30AM +0900, Simon Horman wrote:
> > On Wed, Aug 24, 2011 at 10:06:29AM -0700, Ben Pfaff wrote:
> > > The Python libraries that Open vSwitch installs have been "private"
> > > libraries, in the sense that they
On Fri, Aug 26, 2011 at 08:25:30AM +0900, Simon Horman wrote:
> On Wed, Aug 24, 2011 at 10:06:29AM -0700, Ben Pfaff wrote:
> > The Python libraries that Open vSwitch installs have been "private"
> > libraries, in the sense that they are only really meant to be used by
> > other parts of Open vSwitc
On Wed, Aug 24, 2011 at 10:06:29AM -0700, Ben Pfaff wrote:
> The Python libraries that Open vSwitch installs have been "private"
> libraries, in the sense that they are only really meant to be used by
> other parts of Open vSwitch. Maybe that's a mistake; I guess that
> there is no good reason tha
On Wed, Aug 24, 2011 at 10:06, Ben Pfaff wrote:
> The Python libraries that Open vSwitch installs have been "private"
> libraries, in the sense that they are only really meant to be used by
> other parts of Open vSwitch. Maybe that's a mistake; I guess that
> there is no good reason that they can
The Python libraries that Open vSwitch installs have been "private"
libraries, in the sense that they are only really meant to be used by
other parts of Open vSwitch. Maybe that's a mistake; I guess that
there is no good reason that they cannot be used by other software.
But that's why, until now
