[CRIU] [PATCH 0/6] crit: hex values

[Ruslan Kuprieiev]

Oh, right...
Please, see [PATCH] make: build crit right after config, it solves the 
problem.

On 01/19/2015 02:29 PM, Pavel Emelyanov wrote:
> On 01/16/2015 11:55 PM, Ruslan Kuprieiev wrote:
>> Pavel reported that decimal values for some fields are hard to read,
>> because people used to see hex values in there. Unfortunatelly, json
>> doesn't support hex representation of integers, so we can only store
>> them as hex strings. Not all field need to be represented as hex
>> strings, so this set introduces a custom field option called "criu"
>> to use in our proto files. One should use [(criu).hex = true] to mark
>> which field should be represented as a hex string. pb2dict module
>> from pycriu package will look into field options and if he finds that
>> criu.hex is set to True, it will convert such field to/from hex string.
>> Though, such behaviour is optional and user can request it by specifying
>>   --format hex when calling crit decode("crit encode" in its turn, detects
>> such fields automatically and doesn't require any special cmdline options
>> to be set).
>>
>> This set also contains two patches to mark field that need to be treated
>> as hex numbers, but they don't cover all such fields, so feel free to mark
>> fields that you need.
>>
>> Reported-by: Pavel Emelyanov <xemul at parallels.com>
> And one more thing. After applying this set the command "make"
> compiles CRIU two times.
>