| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| unix | ||
| win32 | ||
| CMakeLists.txt | ||
| README.md | ||
| cli.h | ||
| cmd.c | ||
| cmd.h | ||
| cmd_cat_file.c | ||
| cmd_clone.c | ||
| cmd_hash_object.c | ||
| cmd_help.c | ||
| error.h | ||
| main.c | ||
| opt.c | ||
| opt.h | ||
| opt_usage.c | ||
| opt_usage.h | ||
| progress.c | ||
| progress.h | ||
| sighandler.h |
`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 |
|---|---|---|
| .. | ||
| unix | Loading commit data... | |
| win32 | Loading commit data... | |
| CMakeLists.txt | Loading commit data... | |
| README.md | Loading commit data... | |
| cli.h | Loading commit data... | |
| cmd.c | Loading commit data... | |
| cmd.h | Loading commit data... | |
| cmd_cat_file.c | Loading commit data... | |
| cmd_clone.c | Loading commit data... | |
| cmd_hash_object.c | Loading commit data... | |
| cmd_help.c | Loading commit data... | |
| error.h | Loading commit data... | |
| main.c | Loading commit data... | |
| opt.c | Loading commit data... | |
| opt.h | Loading commit data... | |
| opt_usage.c | Loading commit data... | |
| opt_usage.h | Loading commit data... | |
| progress.c | Loading commit data... | |
| progress.h | Loading commit data... | |
| sighandler.h | Loading commit data... |