diff options
author | Jeff King <peff@peff.net> | 2013-09-18 16:35:13 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-09-18 14:36:40 -0700 |
commit | 643f918d13906cbccdc5ad188767fc7895e30fc1 (patch) | |
tree | d7896325086bc80f5ee80002e78fcf8b44815d22 /contrib/remote-helpers/test-hg-bidi.sh | |
parent | clone: treat "checking connectivity" like other progress (diff) | |
download | tgif-643f918d13906cbccdc5ad188767fc7895e30fc1.tar.xz |
clone: always set transport options
A clone will always create a transport struct, whether we
are cloning locally or using an actual protocol. In the
local case, we only use the transport to get the list of
refs, and then transfer the objects out-of-band.
However, there are many options that we do not bother
setting up in the local case. For the most part, these are
noops, because they only affect the object-fetching stage
(e.g., the --depth option). However, some options do have a
visible impact. For example, giving the path to upload-pack
via "-u" does not currently work for a local clone, even
though we need upload-pack to get the ref list.
We can just drop the conditional entirely and set these
options for both local and non-local clones. Rather than
keep track of which options impact the object versus the ref
fetching stage, we can simply let the noops be noops (and
the cost of setting the options in the first place is not
high).
The one exception is that we also check that the transport
provides both a "get_refs_list" and a "fetch" method. We
will now be checking the former for both cases (which is
good, since a transport that cannot fetch refs would not
work for a local clone), and we tweak the conditional to
check for a "fetch" only when we are non-local.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/remote-helpers/test-hg-bidi.sh')
0 files changed, 0 insertions, 0 deletions