]> source.dussan.org Git - jgit.git/commit
projects / jgit.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 17be66a) | patch
Use BatchRefUpdate for tracking refs in FetchProcess 87/6087/2
authorShawn O. Pearce <spearce@spearce.org>
Wed, 23 May 2012 03:13:11 +0000 (20:13 -0700)
committerShawn O. Pearce <spearce@spearce.org>
Wed, 23 May 2012 03:39:59 +0000 (20:39 -0700)
commit3da13473f7a8baaac6ef1cf965062249c1de141f
tree15252a0bb4edc62c049417b61596afd767f2987dtree | snapshot
parent17be66acdbe662b42a263be77c435945902df968commit | diff
Use BatchRefUpdate for tracking refs in FetchProcess

If there are a lot of references to modify, using BatchRefUpdate can
save time if the underlying storage is able to combine these updates
together. This should speed up initial clone or fetch into an empty
repository, as some projects can have hundreds of release tags, or
hundreds of branch heads.

Change-Id: Iee9af8d5fa19080077d88357c18853540936e940
org.eclipse.jgit.test/tst/org/eclipse/jgit/transport/TransportTest.java diff | blob | history
org.eclipse.jgit/src/org/eclipse/jgit/transport/FetchProcess.java diff | blob | history
org.eclipse.jgit/src/org/eclipse/jgit/transport/RemoteRefUpdate.java diff | blob | history
org.eclipse.jgit/src/org/eclipse/jgit/transport/TrackingRefUpdate.java diff | blob | history
JGit, the Java implementation of git: https://github.com/eclipse-jgit/jgit