)]}'
{
  "commit": "aa064743fa69e2806d5e0af1fab103baa6fa57cd",
  "tree": "9d4bf5f35a18e8d19b0b8bcdcc8258898ac8861f",
  "parents": [
    "fab5de7936f0cc086836a38d2de4374c3df223b4"
  ],
  "author": {
    "name": "Carl Worth",
    "email": "cworth@cworth.org",
    "time": "Tue Feb 21 20:28:50 2006 -0800"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "junkio@cox.net",
    "time": "Tue Feb 21 22:11:50 2006 -0800"
  },
  "message": "git-push: Update documentation to describe the no-refspec behavior.\n\nIt turns out that the git-push documentation didn\u0027t describe what it\nwould do when not given a refspec, (not on the command line, nor in a\nremotes file). This is fairly important for the user who is trying to\nunderstand operations such as:\n\n\tgit clone git://something/some/where\n\t# hack, hack, hack\n\tgit push origin\n\nI tracked the mystery behavior down to git-send-pack and lifted the\nrelevant portion of its documentation up to git-push, (namely that all\nrefs existing both locally and remotely are updated).\n\nSigned-off-by: Carl Worth \u003ccworth@cworth.org\u003e\nSigned-off-by: Junio C Hamano \u003cjunkio@cox.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5b891105b2f9b425db61ee778a7f49eabf3ebcc5",
      "old_mode": 33188,
      "old_path": "Documentation/git-push.txt",
      "new_id": "6f4a48a109acf4fc512aa6dff6254db27fdeeb25",
      "new_mode": 33188,
      "new_path": "Documentation/git-push.txt"
    }
  ]
}