> I don't know how "elegant" this solution from Google is
Christopher,
It's a clever, internal solution to the difficult problem leap seconds create
in any large automated system. That blog entry is 2 years old. The issue has
been discussed at length on the leap second mailing list; you can rea
Christopher,
Obviously GOOG needs a time-nut on their staff!
Interesting stuff!
John W.
On Fri, Sep 20, 2013 at 6:48 PM, Christopher Quarksnow wrote:
> Besides the famous Android stint described in Google bug 5485
> https://code.google.com/p/android/issues/detail?id=5485 that took 2 years
>
Besides the famous Android stint described in Google bug 5485
https://code.google.com/p/android/issues/detail?id=5485 that took 2 years
to fix, so many Android phones system clocks were 15 seconds fast then, I
just found the source of another discrepancy where Google spreads the leap
second offset
