MCPcopy Index your code
hub / github.com/git/git / start_sparse_progress

Function start_sparse_progress

progress.c:312–316  ·  view source on GitHub ↗

* Here "sparse" means that the caller might use some sampling criteria to * decide when to call display_progress() rather than calling it for every * integer value in[0 .. total). In particular, the caller might not call * display_progress() for the last value in the range. * * When "sparse" is set, stop_progress() will automatically force the done * message to show 100%. */

Source from the content-addressed store, hash-verified

310 * message to show 100%.
311 */
312struct progress *start_sparse_progress(struct repository *r,
313 const char *title, uint64_t total)
314{
315 return start_progress_delay(r, title, total, 0, 1);
316}
317
318struct progress *start_delayed_sparse_progress(struct repository *r,
319 const char *title,

Callers 1

verify_midx_fileFunction · 0.85

Calls 1

start_progress_delayFunction · 0.85

Tested by

no test coverage detected