On 09/05/2017 06:05 AM, Thomas Huth wrote:
> On 01.09.2017 20:03, Eric Blake wrote:
>> As a general rule, we prefer avoiding implicit global state
>> because it makes code harder to safely copy and paste without
>> thinking about the global state. It turns out that with the
>> recent changes to li
On 01.09.2017 20:03, Eric Blake wrote:
> As a general rule, we prefer avoiding implicit global state
> because it makes code harder to safely copy and paste without
> thinking about the global state. It turns out that with the
> recent changes to libqos, fw_cfg-test was not even using
> global_qte
On 09/01/2017 03:03 PM, Eric Blake wrote:
As a general rule, we prefer avoiding implicit global state
because it makes code harder to safely copy and paste without
thinking about the global state. It turns out that with the
recent changes to libqos, fw_cfg-test was not even using
global_qtest an
As a general rule, we prefer avoiding implicit global state
because it makes code harder to safely copy and paste without
thinking about the global state. It turns out that with the
recent changes to libqos, fw_cfg-test was not even using
global_qtest any more. Avoid a pointless strdup while at i
