On Tue, 2015-10-20 at 02:34 -0600, Jan Beulich wrote:
> > > > On 20.10.15 at 10:10, wrote:
> > Personally I've never taken the time to familiarize myself with the
> > magnitude of hex numbers vs decimal numbers; so in the case of
> > time, I
> > could easily see that 1000 nanoseconds is about
>>> On 20.10.15 at 11:46, wrote:
> On 20/10/15 09:34, Jan Beulich wrote:
> On 20.10.15 at 10:10, wrote:
>>> On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich wrote:
George, Dario,
it being mostly used in scheduler code, and me considering it quite a
bit easier to compare such
On 20/10/15 09:34, Jan Beulich wrote:
On 20.10.15 at 10:10, wrote:
>> On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich wrote:
>>> George, Dario,
>>>
>>> it being mostly used in scheduler code, and me considering it quite a
>>> bit easier to compare such big numbers when shown in hex I wonder:
>>
>>> On 20.10.15 at 10:10, wrote:
> On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich wrote:
>> George, Dario,
>>
>> it being mostly used in scheduler code, and me considering it quite a
>> bit easier to compare such big numbers when shown in hex I wonder:
>> Do you prefer this to stay PRId64, or would
On 10/20/2015 10:10 AM, George Dunlap wrote:
On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich wrote:
George, Dario,
it being mostly used in scheduler code, and me considering it quite a
bit easier to compare such big numbers when shown in hex I wonder:
Do you prefer this to stay PRId64, or would y
On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich wrote:
> George, Dario,
>
> it being mostly used in scheduler code, and me considering it quite a
> bit easier to compare such big numbers when shown in hex I wonder:
> Do you prefer this to stay PRId64, or would you accept it to be
> changed to PRIx64
