)]}'
{
  "commit": "d96dab868e63cd5a55b50e1d8a23b640e17413bb",
  "tree": "6aed81c6e05d178708857c626135b33a43015a4c",
  "parents": [
    "f0af95f42455b03e3dd83f27f24cb6203eef99ae"
  ],
  "author": {
    "name": "brian m. carlson",
    "email": "sandals@crustytoothpaste.net",
    "time": "Mon May 25 19:59:19 2020 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed May 27 10:07:07 2020 -0700"
  },
  "message": "builtin/ls-remote: initialize repository based on fetch\n\nls-remote may or may not operate within a repository, and as such will\nnot have been initialized with the repository\u0027s hash algorithm.  Even if\nit were, the remote side could be using a different algorithm and we\nwould still want to display those refs properly.  Find the hash\nalgorithm used by the remote side by querying the transport object and\nset our hash algorithm accordingly.\n\nWithout this change, if the remote side is using SHA-256, we truncate\nthe refs to 40 hex characters, since that\u0027s the length of the default\nhash algorithm (SHA-1).\n\nNote that technically this is not a correct setting of the repository\nhash algorithm since, if we are in a repository, it might be one of a\ndifferent hash algorithm from the remote side.  However, our current\ncode paths don\u0027t handle multiple algorithms and won\u0027t for some time, so\nthis is the best we can do.  We rely on the fact that ls-remote never\nmodifies the current repository, which is a reasonable assumption to\nmake.\n\nSigned-off-by: brian m. carlson \u003csandals@crustytoothpaste.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6ef519514bd1a4dfc39b149967ee60dcf14dfbaa",
      "old_mode": 33188,
      "old_path": "builtin/ls-remote.c",
      "new_id": "3a4dd12903206ae47fd4683e3bef1a7371d67d55",
      "new_mode": 33188,
      "new_path": "builtin/ls-remote.c"
    }
  ]
}