On 01/15/2015 09:06 AM, Daniel P. Berrange wrote:
On Thu, Jan 15, 2015 at 08:52:44AM -0700, Eric Blake wrote:
On 01/15/2015 03:51 AM, Jiri Denemark wrote:
On Thu, Jan 15, 2015 at 10:42:39 +, Daniel Berrange wrote:
On Wed, Jan 14, 2015 at 08:08:16PM -0700, Eric Blake wrote:
In some cases,
On 01/15/2015 03:51 AM, Jiri Denemark wrote:
On Thu, Jan 15, 2015 at 10:42:39 +, Daniel Berrange wrote:
On Wed, Jan 14, 2015 at 08:08:16PM -0700, Eric Blake wrote:
In some cases, it is very easy for downstream distros to backport
enum values without requiring a .so bump. Keying the
On Thu, Jan 15, 2015 at 08:52:44AM -0700, Eric Blake wrote:
On 01/15/2015 03:51 AM, Jiri Denemark wrote:
On Thu, Jan 15, 2015 at 10:42:39 +, Daniel Berrange wrote:
On Wed, Jan 14, 2015 at 08:08:16PM -0700, Eric Blake wrote:
In some cases, it is very easy for downstream distros to
On Wed, Jan 14, 2015 at 08:08:16PM -0700, Eric Blake wrote:
In some cases, it is very easy for downstream distros to backport
enum values without requiring a .so bump. Keying the conditional
code off of the upstream version where the enum value was added
is not ideal, because downstream then
On Thu, Jan 15, 2015 at 10:42:39 +, Daniel Berrange wrote:
On Wed, Jan 14, 2015 at 08:08:16PM -0700, Eric Blake wrote:
In some cases, it is very easy for downstream distros to backport
enum values without requiring a .so bump. Keying the conditional
code off of the upstream version
In some cases, it is very easy for downstream distros to backport
enum values without requiring a .so bump. Keying the conditional
code off of the upstream version where the enum value was added
is not ideal, because downstream then has to patch that the feature
is available in their build that
