| commit | cf1f5389ec9eed5453c090cba347f68a3c3da3f7 | |
| author | Taylor Blau <me@ttaylorr.com> | |
| Tue, 30 Mar 2021 15:03:51 +0000 (30 11:03 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 30 Mar 2021 19:16:56 +0000 (30 12:16 -0700) | ||
| tree | f7a5c7c6d5f3bd4dc8ae4422a03f2d5284e0a959 | treesnapshot (tar.gz zip) |
| parent | f7c4d63e35b4358f93efc8d2f124056c246f912e | commitdiff |
builtin/multi-pack-index.c: don't handle 'progress' separately
Now that there is a shared 'flags' member in the options structure,
there is no need to keep track of whether to force progress or not,
since ultimately the decision of whether or not to show a progress meter
is controlled by a bit in the flags member.
Manipulate that bit directly, and drop the now-unnecessary 'progress'
field while we're at it.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Now that there is a shared 'flags' member in the options structure,
there is no need to keep track of whether to force progress or not,
since ultimately the decision of whether or not to show a progress meter
is controlled by a bit in the flags member.
Manipulate that bit directly, and drop the now-unnecessary 'progress'
field while we're at it.
Signed-off-by: Taylor Blau <me@ttaylorr.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/multi-pack-index.c | diffblobblamehistory |