From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Ram Rachum <ram@rachum.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Make `git fetch --all` parallel?
Date: Tue, 11 Oct 2016 15:58:15 -0700 [thread overview]
Message-ID: <xmqq60oy7at4.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZNvTvk4uZa8xhxZABKtzS9A5HoumJ37AacuZnHaZ4+Xw@mail.gmail.com> (Stefan Beller's message of "Tue, 11 Oct 2016 15:50:36 -0700")
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.
next prev parent reply other threads:[~2016-10-11 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 20:12 Make `git fetch --all` parallel? Ram Rachum
2016-10-11 20:53 ` Stefan Beller
2016-10-11 22:37 ` Junio C Hamano
2016-10-11 22:50 ` Stefan Beller
2016-10-11 22:58 ` Junio C Hamano [this message]
2016-10-11 22:58 ` Stefan Beller
2016-10-11 22:59 ` Jeff King
2016-10-11 23:16 ` Ævar Arnfjörð Bjarmason
2016-10-11 23:18 ` Stefan Beller
2016-10-12 1:34 ` Jeff King
2016-10-12 1:52 ` Jeff King
2016-10-12 6:47 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq60oy7at4.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ram@rachum.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).