)]}'
{
  "commit": "537e7d61359233e95d2ca6ef6b9059afca8daa81",
  "tree": "79414a94828c3d321ddd2bd6b2d19ef7d0e242e1",
  "parents": [
    "a9be29c9817067128a2818a609450db6e6722ffd"
  ],
  "author": {
    "name": "Johannes Schindelin",
    "email": "johannes.schindelin@gmx.de",
    "time": "Wed Apr 25 14:29:29 2018 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Apr 26 12:28:43 2018 +0900"
  },
  "message": "sequencer: handle post-rewrite for merge commands\n\nIn the previous patches, we implemented the basic functionality of the\n`git rebase -i --rebase-merges` command, in particular the `merge`\ncommand to create merge commits in the sequencer.\n\nThe interactive rebase is a lot more these days, though, than a simple\ncherry-pick in a loop. For example, it calls the post-rewrite hook (if\nany) after rebasing with a mapping of the old-\u003enew commits.\n\nThis patch implements the post-rewrite handling for the `merge` command\nwe just introduced. The other commands that were added recently (`label`\nand `reset`) do not create new commits, therefore post-rewrite hooks do\nnot need to handle them.\n\nSigned-off-by: Johannes Schindelin \u003cjohannes.schindelin@gmx.de\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e9297122633b83cce5bc880d366c36c6c1d8c574",
      "old_mode": 33188,
      "old_path": "sequencer.c",
      "new_id": "558efc1af6e20e8abfe664d5c647e14216dc127f",
      "new_mode": 33188,
      "new_path": "sequencer.c"
    },
    {
      "type": "modify",
      "old_id": "96853784ec04845a5212a094746c3585fa423ed1",
      "old_mode": 33261,
      "old_path": "t/t3430-rebase-merges.sh",
      "new_id": "e9c5dc1cd95a334448efbda43d09a3ab0456f1e2",
      "new_mode": 33261,
      "new_path": "t/t3430-rebase-merges.sh"
    }
  ]
}