Re: [PATCH] t1092: use GIT_PROGRESS_DELAY for consistent results
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 25, 2021, 08:06 UTC
- Message-ID
- <xmqq35ubfd9y.fsf@gitster.g>
- In-Reply-To
- <87y2c3mezw.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> Well yes, it works in the sense that instead of arbitrary big value for > delay we have the biggerest and largerest value we can manage :) > > I mean why do just that when we can also do this:
Don't make unnecessary changes before any release. If a breakage can be fixed without risking to introduce any new breakages with code change, postpone such a change and save bandwidth to finding and fixing _other_ regressions.
Thanks.