This series adds support for receive.fsckobjects, but on the fetch side of the connection. Perhaps it should be transfer.fsckobjects or fetch.fsckobjects, but git.git doesn't support either of those right now. I mainly need this series because I'm fetching out of untrusted bundles. The content of the bundle has to pass git-fsck for it to be considered safe. The ObjectChecker class covers the same rules as git-fsck does, and is perhaps even stricter on some of the things git-fsck lets slide. I think git-fsck is too lenient in some areas, and I'd like to try and improve the rules more in git.git, but I don't have time for it right now. Shawn O. Pearce (5): Expose RawParseUtils.match to application callers Fix UnpackedObjectLoader.getBytes to return a copy Object validation tests for "jgit fsck" Expose the critical receive configuration options to JGit Honor receive.fsckobjects during any fetch connection .../org/spearce/jgit/lib/ObjectCheckerTest.java | 1294 ++++++++++++++++++++ .../src/org/spearce/jgit/lib/ObjectChecker.java | 352 ++++++ .../src/org/spearce/jgit/lib/ObjectLoader.java | 7 +- .../org/spearce/jgit/lib/PackedObjectLoader.java | 7 - .../src/org/spearce/jgit/lib/RepositoryConfig.java | 10 + .../src/org/spearce/jgit/lib/TransferConfig.java | 56 + .../org/spearce/jgit/lib/UnpackedObjectLoader.java | 4 - .../jgit/transport/BasePackFetchConnection.java | 1 + .../src/org/spearce/jgit/transport/IndexPack.java | 60 +- .../src/org/spearce/jgit/transport/Transport.java | 24 + .../spearce/jgit/transport/TransportBundle.java | 10 +- .../jgit/transport/WalkFetchConnection.java | 26 +- .../src/org/spearce/jgit/util/RawParseUtils.java | 23 +- 13 files changed, 1842 insertions(+), 32 deletions(-) create mode 100644 org.spearce.jgit.test/tst/org/spearce/jgit/lib/ObjectCheckerTest.java create mode 100644 org.spearce.jgit/src/org/spearce/jgit/lib/ObjectChecker.java create mode 100644 org.spearce.jgit/src/org/spearce/jgit/lib/TransferConfig.java -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
