)]}'
{
  "commit": "c7bafad10d294cc0b26ab6171efd89dd9b132f70",
  "tree": "faad73b1772cc8632ceb02ad4fb41e4ca2a5227b",
  "parents": [
    "0b5ea163d21163343579cd6eb9274ccc2190a0fe"
  ],
  "author": {
    "name": "Shawn O. Pearce",
    "email": "spearce@spearce.org",
    "time": "Mon Mar 12 13:03:47 2007 -0400"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "spearce@spearce.org",
    "time": "Mon Mar 12 13:03:47 2007 -0400"
  },
  "message": "git-gui: Allow committing empty merges\n\nJohannes Sixt noticed that git-gui would not let the user commit\na merge created by `git merge -s ours` as the ours strategy does\nnot alter the tree (that is HEAD^1^{tree} \u003d HEAD^{tree} after the\nmerge).  The same issue arises from amending such a merge commit.\n\nWe now permit an empty commit (no changed files) if we are doing\na merge commit.  Core Git does this with its command line based\ngit-commit tool, so it makes sense for the GUI to do the same.\n\nSigned-off-by: Shawn O. Pearce \u003cspearce@spearce.org\u003e",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1981827a8e8bcc2b2e43598bb06e3e6c87bd4d1d",
      "old_mode": 33261,
      "old_path": "git-gui.sh",
      "new_id": "0e448007f7c3cd4a109dd5920bc9d1fc6a21b483",
      "new_mode": 33261,
      "new_path": "git-gui.sh"
    }
  ]
}