Re: Make `git fetch --all` parallel?

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 11, 2016, 22:58 UTC
Message-ID: <xmqq60oy7at4.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kZNvTvk4uZa8xhxZABKtzS9A5HoumJ37AacuZnHaZ4+Xw@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

> Why did you put a "sleep 2" below?

The assumption was to fetch from faster and near the center of the project universe early, so by giving them head-start, fetches that start in later rounds may have chance to see newly updated remote tracking refs when telling the poorer other ends what we have.

> At the very least we would need a similar thing as Jeff recently sent for the
> push case with objects quarantined and then made available in one go?

There is no race; ref updates are done only after objects are fully finalized. You can do the quarantine but that would defeat the "let ones from the center of universe finish early so later ones from poor periphery have more .have's to work with" idea, I suspect.