)]}'
{
  "commit": "4eb56b56e7cb35ec1ff152f3b6e6c4533d48cbdd",
  "tree": "11ba87053b749e75e8e105fb720b430f24041ec5",
  "parents": [
    "71ca53e8125e36efbda17293c50027d31681a41f"
  ],
  "author": {
    "name": "brian m. carlson",
    "email": "sandals@crustytoothpaste.net",
    "time": "Sun Jan 10 19:04:48 2021 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Mon Jan 11 12:14:07 2021 -0800"
  },
  "message": "docs: rephrase and clarify the git status --short format\n\nThe table describing the porcelain format in git-status(1) is helpful,\nbut it\u0027s not completely clear what the three sections mean, even to\nsome contributors.  As a result, users are unable to find how to detect\ncommon cases like merge conflicts programmatically.\n\nLet\u0027s improve this situation by rephrasing to be more explicit about\nwhat each of the sections in the table means, to tell users in plain\nlanguage which cases are occurring, and to describe what \"unmerged\"\nmeans.\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": "7731b45f078e92e01df48d47d9f9abf9d1d931c1",
      "old_mode": 33188,
      "old_path": "Documentation/git-status.txt",
      "new_id": "c0764e850a44adde9499c6e601dace9320116f38",
      "new_mode": 33188,
      "new_path": "Documentation/git-status.txt"
    }
  ]
}