"William Baker via GitGitGadget" <gitgitgad...@gmail.com> writes:
> William Baker (6):
> midx: add MIDX_PROGRESS flag Add the MIDX_PROGRESS flag and update the
> write|verify|expire|repack functions in midx.h to accept a flags
> parameter. The MIDX_PROGRESS flag indicates whether the caller of
> the function would like progress information to be displayed. This
> patch only changes the method prototypes and does not change the
> functionality. The functionality change will be handled by a later
> patch.
> midx: add progress to write_midx_file Add progress to write_midx_file.
> Progress is displayed when the MIDX_PROGRESS flag is set.
> midx: add progress to expire_midx_packs Add progress to
> expire_midx_packs. Progress is displayed when the MIDX_PROGRESS
> flag is set.
> midx: honor the MIDX_PROGRESS flag in verify_midx_file Update
> verify_midx_file to only display progress when the MIDX_PROGRESS
> flag is set.
> midx: honor the MIDX_PROGRESS flag in midx_repack Update midx_repack
> to only display progress when the MIDX_PROGRESS flag is set.
> multi-pack-index: add [--[no-]progress] option. Add the
> --[no-]progress option to git multi-pack-index. Pass the
> MIDX_PROGRESS flag to the subcommand functions when progress should
> be displayed by multi-pack-index. The progress feature was added to
> 'verify' in 144d703 ("multi-pack-index: report progress during
> 'verify'", 2018-09-13) but some subcommands were not updated to
> display progress, and the ability to opt-out was overlooked.
Do all of these commits have overly long title with no body recorded
in the commit objects, or is this just a mail sending program
screwing up?
