On Tue, May 14, 2019 at 10:37:55AM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrangé (berra...@redhat.com) wrote:
> > On Tue, May 14, 2019 at 08:02:49AM +0200, Markus Armbruster wrote:
> > > Eric Blake writes:
> > >
> > > > On 5/13/19 8:53 AM, Markus Armbruster wrote:
> > > >
> > > >>>
On Tue, May 14, 2019 at 10:43:31 +0100, Daniel Berrange wrote:
> On Tue, May 14, 2019 at 10:37:55AM +0100, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> > > On Tue, May 14, 2019 at 08:02:49AM +0200, Markus Armbruster wrote:
> > > > Eric Blake writes:
[...]
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Tue, May 14, 2019 at 08:02:49AM +0200, Markus Armbruster wrote:
> > Eric Blake writes:
> >
> > > On 5/13/19 8:53 AM, Markus Armbruster wrote:
> > >
> > >>> We have a few options
> > >>>
> > >>> 1. Use string format for values > 2^53-1, int f
On Tue, May 14, 2019 at 08:02:49AM +0200, Markus Armbruster wrote:
> Eric Blake writes:
>
> > On 5/13/19 8:53 AM, Markus Armbruster wrote:
> >
> >>> We have a few options
> >>>
> >>> 1. Use string format for values > 2^53-1, int format below that
> >>> 2. Use string format for all fields which
Eric Blake writes:
> On 5/13/19 8:53 AM, Markus Armbruster wrote:
>
>>> We have a few options
>>>
>>> 1. Use string format for values > 2^53-1, int format below that
>>> 2. Use string format for all fields which are 64-bit ints whether
>>> signed or unsigned
>>> 3. Use string format for al
On 5/13/19 8:53 AM, Markus Armbruster wrote:
>> We have a few options
>>
>> 1. Use string format for values > 2^53-1, int format below that
>> 2. Use string format for all fields which are 64-bit ints whether
>> signed or unsigned
>> 3. Use string format for all fields which are integers, e