summaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit.packaging/org.eclipse.jgit.junit.feature/.settings
diff options
context:
space:
mode:
authorChristian Halstrick <christian.halstrick@sap.com>2014-09-25 17:29:35 +0200
committerMatthias Sohn <matthias.sohn@sap.com>2014-09-25 19:01:42 -0400
commitfa4f00b7ed248d420ba12c576f944e873a3b8095 (patch)
tree66cf119a1296933b2ca8d085e66804291bc28ac8 /org.eclipse.jgit.packaging/org.eclipse.jgit.junit.feature/.settings
parent6d00f0a09c67421d4ac9960c568f9c18ceb4a6a4 (diff)
downloadjgit-fa4f00b7ed248d420ba12c576f944e873a3b8095.tar.gz
jgit-fa4f00b7ed248d420ba12c576f944e873a3b8095.zip
Fix PackWriterBitmapWalker handling non-existing uninteresting objects
When writing new packs it should be allowed to specify objects as "have" (objects which should not be included in the pack) which do not exist in the local repository. This works with the traditional PackWriter, but when PackWriter was working on a repository with bitmap indexes and used PackWriterBitmapWalker then this feature was broken. Non-existing "have" objects lead to MissingObjectExceptions. That broke push and Gerrit replication. When the replication target had branches unknown to the replication source then the source repository wanted to build pack files where "have" included branch-tips which were unknown in the source repository. Bug: 427107 Change-Id: I6b6598a1ec49af68aa77ea6f1f06e827982ea4ac Also-by: Matthias Sohn <matthias.sohn@sap.com>
Diffstat (limited to 'org.eclipse.jgit.packaging/org.eclipse.jgit.junit.feature/.settings')
0 files changed, 0 insertions, 0 deletions