[PATCH 0/2] trivial progress.c API usage fixes · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
[PATCH 2/2] read-cache: fix incorrect count and progress bar stalling · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
Re: [PATCH 2/2] read-cache: fix incorrect count and progress bar stalling · Derrick Stolee <hidden> · 2021-06-07
Re: [PATCH 2/2] read-cache: fix incorrect count and progress bar stalling · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
Re: [PATCH 2/2] read-cache: fix incorrect count and progress bar stalling · René Scharfe <hidden> · 2021-06-07
Re: [PATCH 2/2] read-cache: fix incorrect count and progress bar stalling · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
[PATCH 1/2] read-cache.c: don't guard calls to progress.c API · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
Re: [PATCH 1/2] read-cache.c: don't guard calls to progress.c API · Derrick Stolee <hidden> · 2021-06-07
Re: [PATCH 1/2] read-cache.c: don't guard calls to progress.c API · Ævar Arnfjörð Bjarmason <hidden> · 2021-06-07
Re: [PATCH 1/2] read-cache.c: don't guard calls to progress.c API · Derrick Stolee <hidden> · 2021-06-07

Re: [PATCH 1/2] read-cache.c: don't guard calls to progress.c API

From: Derrick Stolee <hidden>
Date: 2021-06-07 15:28:07

On 6/7/2021 10:43 AM, Ævar Arnfjörð Bjarmason wrote:

Don't guard the calls to the progress.c API with "if (progress)". The
API itself will check this. This doesn't change any behavior, but
makes this code consistent with the rest of the codebase.

Since stop_progress() closes a trace2 region, this actually
does make a change in behavior, I think. In a good way.

Thanks,
-Stolee

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help