Eric Blake writes:
> On 03/08/2016 09:46 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> Every non-implicit entity is associated with an 'info'
>>> dictionary, but it is not easy to reverse-engineer the name of
>>> the top-most entity associated with that 'info'. Our use of
>>> 'case
On 03/08/2016 09:46 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Every non-implicit entity is associated with an 'info'
>> dictionary, but it is not easy to reverse-engineer the name of
>> the top-most entity associated with that 'info'. Our use of
>> 'case_whitelist' (added in commit
Eric Blake writes:
> Every non-implicit entity is associated with an 'info'
> dictionary, but it is not easy to reverse-engineer the name of
> the top-most entity associated with that 'info'. Our use of
> 'case_whitelist' (added in commit 893e1f2) is thus currently
> tied to the owner of a membe
Every non-implicit entity is associated with an 'info'
dictionary, but it is not easy to reverse-engineer the name of
the top-most entity associated with that 'info'. Our use of
'case_whitelist' (added in commit 893e1f2) is thus currently
tied to the owner of a member instead; but as the previous
