On Mon, Sep 16, 2013 at 03:15:01PM -0700, Ben Pfaff wrote:
> Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in
> log messages.) introduced milliseconds to log messages by default, but the
> Python version did not ensure that milliseconds were always formatted with
> 3 digit
Thanks guys.
:: psi
On Sep 17, 2013, at 10:05 AM, Ben Pfaff wrote:
> On Tue, Sep 17, 2013 at 09:59:58AM -0700, Gurucharan Shetty wrote:
>> On Mon, Sep 16, 2013 at 3:15 PM, Ben Pfaff wrote:
>>> Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in
>>> log messages.) introdu
On Mon, Sep 16, 2013 at 3:15 PM, Ben Pfaff wrote:
> Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in
> log messages.) introduced milliseconds to log messages by default, but the
> Python version did not ensure that milliseconds were always formatted with
> 3 digits, so 3.
On Tue, Sep 17, 2013 at 09:59:58AM -0700, Gurucharan Shetty wrote:
> On Mon, Sep 16, 2013 at 3:15 PM, Ben Pfaff wrote:
> > Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in
> > log messages.) introduced milliseconds to log messages by default, but the
> > Python version di
Commit 2b31d8e713de7 (vlog: Report timestamps in millisecond resolution in
log messages.) introduced milliseconds to log messages by default, but the
Python version did not ensure that milliseconds were always formatted with
3 digits, so 3.001 was formatted as "3.1" and 3.012 as "3.12", and so on.
