Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
clar | ||
headertest | ||
libgit2 | ||
resources | ||
util | ||
CMakeLists.txt | ||
README.md |
`git__timer` is now `git_time_monotonic`, and returns milliseconds since an arbitrary epoch. Using a floating point to store the number of seconds elapsed was clever, as it better supports the wide range of precision from the different monotonic clocks of different systems. But we're a version control system, not a real-time clock. Milliseconds is a good enough precision for our work _and_ it's the units that system calls like `poll` take and that our users interact with. Make `git_time_monotonic` return the monotonically increasing number of milliseconds "ticked" since some arbitrary epoch.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | Loading commit data... | |
clar | Loading commit data... | |
headertest | Loading commit data... | |
libgit2 | Loading commit data... | |
resources | Loading commit data... | |
util | Loading commit data... | |
CMakeLists.txt | Loading commit data... | |
README.md | Loading commit data... |