Name |
Last commit
|
Last update |
---|---|---|
.. | ||
clar | ||
clar.c | ||
clar.h | ||
clar_libgit2.c | ||
clar_libgit2.h | ||
clar_libgit2_timer.c | ||
clar_libgit2_timer.h | ||
clar_libgit2_trace.c | ||
clar_libgit2_trace.h | ||
generate.py | ||
main.c |
`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 |
---|---|---|
.. | ||
clar | Loading commit data... | |
clar.c | Loading commit data... | |
clar.h | Loading commit data... | |
clar_libgit2.c | Loading commit data... | |
clar_libgit2.h | Loading commit data... | |
clar_libgit2_timer.c | Loading commit data... | |
clar_libgit2_timer.h | Loading commit data... | |
clar_libgit2_trace.c | Loading commit data... | |
clar_libgit2_trace.h | Loading commit data... | |
generate.py | Loading commit data... | |
main.c | Loading commit data... |