diff options
| author | Junio C Hamano <gitster@pobox.com> | 2018-08-16 01:08:25 +0300 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2018-08-16 01:08:25 +0300 |
| commit | d6628c99faf0de4d34c44f815d2aaa7dee38a300 (patch) | |
| tree | 6415c1ab446fee432da35f1598f153c06385a976 /builtin/fetch.c | |
| parent | 7d020f5a78a1ae7ff47d65a2adc79171c0cf9cb7 (diff) | |
| parent | 2b554353a5f0463dec44b827e2d1423b698d06d3 (diff) | |
Merge branch 'jt/tag-following-with-proto-v2-fix'
The wire-protocol v2 relies on the client to send "ref prefixes" to
limit the bandwidth spent on the initial ref advertisement. "git
fetch $remote branch:branch" that asks tags that point into the
history leading to the "branch" automatically followed sent to
narrow prefix and broke the tag following, which has been fixed.
* jt/tag-following-with-proto-v2-fix:
fetch: send "refs/tags/" prefix upon CLI refspecs
t5702: test fetch with multiple refspecs at a time
Diffstat (limited to 'builtin/fetch.c')
| -rw-r--r-- | builtin/fetch.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/builtin/fetch.c b/builtin/fetch.c index 34d2bd123b..e03a1db1a3 100644 --- a/builtin/fetch.c +++ b/builtin/fetch.c @@ -1192,7 +1192,7 @@ static int do_fetch(struct transport *transport, refspec_ref_prefixes(&transport->remote->fetch, &ref_prefixes); if (ref_prefixes.argc && - (tags == TAGS_SET || (tags == TAGS_DEFAULT && !rs->nr))) { + (tags == TAGS_SET || (tags == TAGS_DEFAULT))) { argv_array_push(&ref_prefixes, "refs/tags/"); } |