)]}'
{
  "commit": "120b1eb7314687375e0a229e102ffd194cae0e06",
  "tree": "10563de5795b5b4c56a53aa988247e061c18e797",
  "parents": [
    "9a1b7474d6babad5fabed9a2926a57d875f3820b"
  ],
  "author": {
    "name": "Elijah Newren",
    "email": "newren@gmail.com",
    "time": "Wed Mar 11 15:30:23 2020 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Mar 11 12:11:08 2020 -0700"
  },
  "message": "git-rebase.txt: highlight backend differences with commit rewording\n\nAs noted by Junio:\n    Back when \"git am\" was written, it was not considered a bug that the\n    \"git am --resolved\" option did not offer the user a chance to update\n    the log message to match the adjustment of the code the user made,\n    but honestly, I\u0027d have to say that it is a bug in \"git am\" in that\n    over time it wasn\u0027t adjusted to the new world order where we\n    encourage users to describe what they did when the automation\n    hiccuped by opening an editor.  These days, even when automation\n    worked well (e.g. a clean auto-merge with \"git merge\"), we open an\n    editor.  The world has changed, and so should the expectations.\n\nJunio also suggested providing a workaround such as allowing --no-edit\ntogether with git rebase --continue, but that should probably be done in\na patch after the git-2.26.0 release.  For now, just document the known\ndifference in the Behavioral Differences section.\n\nSigned-off-by: Elijah Newren \u003cnewren@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8c1f4b826809e922d9864eb0ed88daa737f4c217",
      "old_mode": 33188,
      "old_path": "Documentation/git-rebase.txt",
      "new_id": "f7a6033607fa558dfd5a0437d7b4327ff1c44c78",
      "new_mode": 33188,
      "new_path": "Documentation/git-rebase.txt"
    }
  ]
}