summaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit.junit.http
diff options
context:
space:
mode:
authorShawn Pearce <spearce@spearce.org>2017-01-03 14:23:57 -0800
committerShawn Pearce <spearce@spearce.org>2017-01-03 14:46:41 -0800
commitdb776102566a472e76073997cddf5417cc02389b (patch)
treee4748d099dcfb7c1fb50b68db7ffee410b81f476 /org.eclipse.jgit.junit.http
parent6087031469487e23b5e7055d0d4e65e2ce96fcbd (diff)
downloadjgit-db776102566a472e76073997cddf5417cc02389b.tar.gz
jgit-db776102566a472e76073997cddf5417cc02389b.zip
Pack refs/tags/ with refs/heads/
This fixes a nasty performance issue for repositories that have many objects referenced through refs/tags/, but not in refs/heads/. Situations like this can arise when a project has made releases like refs/tags/v1.0, and then decides to orphan history and start over for version 2. The v1.0 objects are not reachable from master anymore, but are still live due to the v1.0 tag. When tags are packed in the GC_OTHER pack, bitmaps are not able to cover the repository's contents. This may cause very slow counting times during git clone, as the server must enumerate the ancient history under refs/tags/ to respond to the client. Clients by default always ask for all tags when asking for all heads during clone. This has been true since git-core commit 8434c2f1afedb (Apr 27 2008), when clone was converted to a builtin. Including tags in the main GC pack should still allow servers to benefit from the fast full pack reuse path when serving a clone to a client. Change-Id: I22e29517b5bc6fa3d6b19a19f13bef0c68afdca3
Diffstat (limited to 'org.eclipse.jgit.junit.http')
0 files changed, 0 insertions, 0 deletions