- Original Message -
From: Nir Soffer nsof...@redhat.com
To: Francesco Romani from...@redhat.com
Cc: engine-de...@ovirt.org devel@ovirt.org
Sent: Thursday, November 13, 2014 9:35:30 PM
Subject: Re: [ovirt-devel] [VDSM] [JSONRPC] early, coarse grained benchmarks
[...]
I'm profiling
- Original Message -
From: Francesco Romani from...@redhat.com
To: engine-de...@ovirt.org devel@ovirt.org
Cc: Nir Soffer nsof...@redhat.com
Sent: Monday, November 17, 2014 11:47:40 AM
Subject: Re: [ovirt-devel] [VDSM] [JSONRPC] early, coarse grained benchmarks
- Original
Hi
Please note that I have added a common function to ease handling of
configuration settings:
signature : fn_db_add_config_value_for_versions_up_to(v_option_name, v_val ,
v_version )
so, for example, if you want to add a new feature F1 flag, which is true only
for 3.6, to _config.sql
- Original Message -
From: Eli Mesika emes...@redhat.com
To: engine-de...@ovirt.org devel@ovirt.org
Sent: Monday, November 17, 2014 12:40:53 PM
Subject: [ovirt-devel] [db] add config key with same value to multiple
versions
Hi
Please note that I have added a common
On 17/11/14 08:41, Itamar Heim wrote:
1) Is this still an issue?
Yes of course, or is it implemented yet?
2) Can we afford to dilute the focus we have as it is hard enough to
stabilize the currently supported distro's? is it worth the
potential impact?
In general: Software which
Hi,
I just merged [1], which causes *ListModels to be managed by GIN. What does
this mean for you? Well if you are creating a new ListModel you should also
have them managed by GIN as the CommonModel no longer manages them. If you
have any problems with this let me know I will walk you through
Il 17/11/2014 14:22, Sven Kieske ha scritto:
On 17/11/14 08:41, Itamar Heim wrote:
1) Is this still an issue?
Yes of course, or is it implemented yet?
2) Can we afford to dilute the focus we have as it is hard enough to
stabilize the currently supported distro's? is it worth the
On Mon, Nov 10, 2014 at 08:24:40AM -0500, Ondřej Svoboda wrote:
Hi,
I am in favor of tagging e.g. the commit introducing the hook in question [1]
with v4.16.99.
(Similarly, in the message to ovirt-users [2] I suggested that anyone
interested in the hook tag their master branch with
