From: Phillip Wood <phillip.wood@xxxxxxxxxxxxx> Clarify what happens when an object exists in more than one pack, but not in the preferred pack. If the user does not pass a preferred pack then the pack with the lowest mtime is chosen as the preferred pack. For objects that are not in the preferred pack the pack with the highest mtime is used. "git multi-pack-index repack" relies on this behavior. If ties were resolved in favor of the oldest pack as the current documentation suggests the multi-pack index would not reference any of the objects in the pack created by "git multi-pack-index repack". Signed-off-by: Phillip Wood <phillip.wood@xxxxxxxxxxxxx> --- Documentation/git-multi-pack-index.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/git-multi-pack-index.adoc b/Documentation/git-multi-pack-index.adoc index 631d5c7d15c..1f016b2f682 100644 --- a/Documentation/git-multi-pack-index.adoc +++ b/Documentation/git-multi-pack-index.adoc @@ -40,8 +40,10 @@ write:: --preferred-pack=<pack>:: Optionally specify the tie-breaking pack used when multiple packs contain the same object. `<pack>` must - contain at least one object. If not given, ties are - broken in favor of the pack with the lowest mtime. + contain at least one object. If not given the pack with + the lowest mtime is used as the preferred pack. Ties + for objects that are not contained in the preferred + are resolved in favor of the pack with the newest mtime. --[no-]bitmap:: Control whether or not a multi-pack bitmap is written. -- 2.49.0.897.gfad3eb7d210
