mirror of
https://github.com/git/git
synced 2024-08-24 18:26:02 +00:00
pack-objects: allow "thin" packs to exceed depth limits
When creating a new pack to be used in .git/objects/pack/ directory, we carefully count the depth of deltified objects to be reused, so that the generated pack does not to exceed the specified depth limit for runtime efficiency. However, when we are generating a thin pack that does not contain base objects, such a pack can only be used during network transfer that is expanded on the other end upon reception, so being careful and artificially cutting the delta chain does not buy us anything except increased bandwidth requirement. This patch disables the delta chain depth limit check when reusing an existing delta. Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
parent
1d6b38cc76
commit
b76f6b6278
|
@ -663,10 +663,23 @@ static void get_object_details(void)
|
|||
prepare_pack_ix();
|
||||
for (i = 0, entry = objects; i < nr_objects; i++, entry++)
|
||||
check_object(entry);
|
||||
for (i = 0, entry = objects; i < nr_objects; i++, entry++)
|
||||
if (!entry->delta && entry->delta_child)
|
||||
entry->delta_limit =
|
||||
check_delta_limit(entry, 1);
|
||||
|
||||
if (nr_objects == nr_result) {
|
||||
/*
|
||||
* Depth of objects that depend on the entry -- this
|
||||
* is subtracted from depth-max to break too deep
|
||||
* delta chain because of delta data reusing.
|
||||
* However, we loosen this restriction when we know we
|
||||
* are creating a thin pack -- it will have to be
|
||||
* expanded on the other end anyway, so do not
|
||||
* artificially cut the delta chain and let it go as
|
||||
* deep as it wants.
|
||||
*/
|
||||
for (i = 0, entry = objects; i < nr_objects; i++, entry++)
|
||||
if (!entry->delta && entry->delta_child)
|
||||
entry->delta_limit =
|
||||
check_delta_limit(entry, 1);
|
||||
}
|
||||
}
|
||||
|
||||
typedef int (*entry_sort_t)(const struct object_entry *, const struct object_entry *);
|
||||
|
|
Loading…
Reference in a new issue