)]}'
{
  "commit": "a060705d94461fdaa9512217d584bcb7fe3a109a",
  "tree": "61b8ed691e1101ce6c1aee246151cee4025756f5",
  "parents": [
    "0d1bd1dfb37ef25e1911777c94129fc769ffec38"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Oct 17 20:08:51 2023 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Oct 17 22:09:54 2023 -0700"
  },
  "message": "commit: do not use cryptic \"new_index\" in end-user facing messages\n\nThese error messages say \"new_index\" as if that spelling has some\nsignificance to the end users (e.g. the file \"$GIT_DIR/new_index\"\nhas some issues), but that is not the case at all.  The i18n folks\nwere made to include the word literally in the translated messages,\nwhich was not a good idea at all.  Spell it \"new index\", as we are\njust telling the users that we failed to create a new index file.\nThe term is expected to be translated to the end-users\u0027 languages,\nnot left as if it were a literal file name.\n\nThis dates all the way back to the first re-implemenation of \"git\ncommit\" command in C (the scripted version did not have such wording\nin its error messages), in f5bbc322 (Port git commit to C.,\n2007-11-08).\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "985a0445b7897c936cc69e828d1e9f4ad98abaf7",
      "old_mode": 33188,
      "old_path": "builtin/commit.c",
      "new_id": "7abd566bc780642f9a5e7d1b2751b3f85eed48a9",
      "new_mode": 33188,
      "new_path": "builtin/commit.c"
    }
  ]
}