THIS IS A TEST INSTANCE ONLY! REPOSITORIES CAN BE DELETED AT ANY TIME!

Browse Source

send-pack: never fetch when checking exclusions

When building the packfile to be sent, send_pack() is given a list of
remote refs to be used as exclusions. For each ref, it first checks if
the ref exists locally, and if it does, passes it with a "^" prefix to
pack-objects. However, in a partial clone, the check may trigger a lazy
fetch.

The additional commit ancestry information obtained during such fetches
may show that certain objects that would have been sent are already
known to the server, resulting in a smaller pack being sent. But this is
at the cost of fetching from many possibly unrelated refs, and the lazy
fetches do not help at all in the typical case where the client is
up-to-date with the upstream of the branch being pushed.

Ensure that these lazy fetches do not occur.

Signed-off-by: Jonathan Tan <jonathantanmy@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
tags/v2.24.0-rc0
Jonathan Tan Junio C Hamano 1 month ago
parent
commit
d8bc1a518a
1 changed files with 2 additions and 1 deletions
  1. +2
    -1
      send-pack.c

+ 2
- 1
send-pack.c View File

@@ -40,7 +40,8 @@ int option_parse_push_signed(const struct option *opt,

static void feed_object(const struct object_id *oid, FILE *fh, int negative)
{
if (negative && !has_object_file(oid))
if (negative &&
!has_object_file_with_flags(oid, OBJECT_INFO_SKIP_FETCH_OBJECT))
return;

if (negative)


Loading…
Cancel
Save