)]}'
{
  "commit": "be4ca290570f9173db64ea1f925b5b3831c6efed",
  "tree": "3c010d3574792fba13c5b6a2c177dfb01c628705",
  "parents": [
    "6a2c2f8d34fa1e8f3bb85d159d354810ed63692e"
  ],
  "author": {
    "name": "David Turner",
    "email": "dturner@twosigma.com",
    "time": "Thu Apr 20 16:41:18 2017 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Apr 20 22:06:00 2017 -0700"
  },
  "message": "Increase core.packedGitLimit\n\nWhen core.packedGitLimit is exceeded, git will close packs.  If there\nis a repack operation going on in parallel with a fetch, the fetch\nmight open a pack, and then be forced to close it due to\npackedGitLimit being hit.  The repack could then delete the pack\nout from under the fetch, causing the fetch to fail.\n\nIncrease core.packedGitLimit\u0027s default value to prevent\nthis.\n\nOn current 64-bit x86_64 machines, 48 bits of address space are\navailable.  It appears that 64-bit ARM machines have no standard\namount of address space (that is, it varies by manufacturer), and IA64\nand POWER machines have the full 64 bits.  So 48 bits is the only\nlimit that we can reasonably care about.  We reserve a few bits of the\n48-bit address space for the kernel\u0027s use (this is not strictly\nnecessary, but it\u0027s better to be safe), and use up to the remaining\n45.  No git repository will be anywhere near this large any time soon,\nso this should prevent the failure.\n\nHelped-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: David Turner \u003cdturner@twosigma.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8a4a3f85e7ba0a658420c477e1af82e804d7fd36",
      "old_mode": 33188,
      "old_path": "git-compat-util.h",
      "new_id": "1c5de153a528ada32435b8328e6176918aed6b21",
      "new_mode": 33188,
      "new_path": "git-compat-util.h"
    }
  ]
}