On 06/07/2017 08:03 PM, Juan Quintela wrote:
> Halil Pasic wrote:
>> On 06/01/2017 01:32 PM, Cornelia Huck wrote:
>>> On Thu, 1 Jun 2017 11:35:27 +0200
>>> Halil Pasic wrote:
>>>
>
>
> I was about to suggest to move css from pointer
Halil Pasic wrote:
> On 06/01/2017 01:32 PM, Cornelia Huck wrote:
>> On Thu, 1 Jun 2017 11:35:27 +0200
>> Halil Pasic wrote:
>>
I was about to suggest to move css from pointer to an embedded struct,
and then noticed that
On 06/01/2017 01:32 PM, Cornelia Huck wrote:
> On Thu, 1 Jun 2017 11:35:27 +0200
> Halil Pasic wrote:
>
>> On 05/31/2017 08:52 PM, Juan Quintela wrote:
>>> Halil Pasic wrote:
Although we have recently vmstatified the migration of some
On Mon, 29 May 2017 15:55:17 +0200
Halil Pasic wrote:
> Although we have recently vmstatified the migration of some css
> infrastructure, for some css entities there is still state to be
> migrated left, because the focus was keeping migration stream
> compatibility
On Thu, 1 Jun 2017 11:35:27 +0200
Halil Pasic wrote:
> On 05/31/2017 08:52 PM, Juan Quintela wrote:
> > Halil Pasic wrote:
> >> Although we have recently vmstatified the migration of some css
> >> infrastructure, for some css entities there
On 05/31/2017 08:52 PM, Juan Quintela wrote:
> Halil Pasic wrote:
>> Although we have recently vmstatified the migration of some css
>> infrastructure, for some css entities there is still state to be
>> migrated left, because the focus was keeping migration stream
>>
Halil Pasic wrote:
> Although we have recently vmstatified the migration of some css
> infrastructure, for some css entities there is still state to be
> migrated left, because the focus was keeping migration stream
> compatibility (that is basically everything as-is).
Although we have recently vmstatified the migration of some css
infrastructure, for some css entities there is still state to be
migrated left, because the focus was keeping migration stream
compatibility (that is basically everything as-is).
Let us add vmstate helpers and extend existing