)]}'
{
  "commit": "a08b1d62b0c58c795b3ddbe34ea1f68786b95c82",
  "tree": "41ea597bdcbef73f5475f7906551d8748a3b2910",
  "parents": [
    "465e73fff380808f0ba3fb17984ab8636afb6405",
    "2f215ff10bdf02f6c760ea34968fc39ae75ae449"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Oct 19 13:34:08 2018 +0900"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Oct 19 13:34:08 2018 +0900"
  },
  "message": "Merge branch \u0027jt/cache-tree-allow-missing-object-in-partial-clone\u0027\n\nIn a partial clone that will lazily be hydrated from the\noriginating repository, we generally want to avoid \"does this\nobject exist (locally)?\" on objects that we deliberately omitted\nwhen we created the clone.  The cache-tree codepath (which is used\nto write a tree object out of the index) however insisted that the\nobject exists, even for paths that are outside of the partial\ncheckout area.  The code has been updated to avoid such a check.\n\n* jt/cache-tree-allow-missing-object-in-partial-clone:\n  cache-tree: skip some blob checks in partial clone\n",
  "tree_diff": []
}