On 2026-08-22 12:48:22 +0200, Vincent Lefevre wrote: > On 2026-08-22 09:31:49 +0200, Oswald Buddenhagen via Mutt-dev wrote: > > On Fri, Aug 21, 2026 at 03:25:10PM +0200, Vincent Lefevre wrote: > > > No, this is not the same thing. The mtime has had a nanosecond > > > precision for years. But the granularity changed recently. > > > > > and my language intuition says that this is just wrong. > > > > Teh Bot says https://chatgpt.com/share/6a893fa3-b1e4-83eb-a43d-f38fc2b1c2c0 > > which seems to agree. > > Well, that's ChatGPT. > > In the context of clocks, the granularity is how often a clock is > updated (the smallest amount that can be obtained between 2 ticks).
And see https://shavinanjitha.medium.com/the-timeless-challenge-synchronizing-clocks-in-distributed-systems-6bfd32cdebe4 "Assigning timestamps to events isn't just about the presence of a clock — it's also about its granularity. The resolution of a clock is the smallest interval it can distinguish between two successive time points." -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
