)]}'
{
  "commit": "79b1138e7894ea048008f6b99908f5cd36e94949",
  "tree": "22ce33a3dc57a1f22208a104bf700efacce45fd7",
  "parents": [
    "c95b3ad9ea310ec89e31a21edecaaf2c374e2c46"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Mar 04 02:02:35 2008 -0800"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Mar 05 10:32:01 2008 -0800"
  },
  "message": "fsck.c: fix bogus \"empty tree\" check\n\nba002f3 (builtin-fsck: move common object checking code to fsck.c) did\nmore than what it claimed to.  Most notably, it wrongly made an empty tree\nobject an error by pretending to only move code from fsck_tree() in\nbuiltin-fsck.c to fsck_tree() in fsck.c, but in fact adding a bogus check\nto barf on an empty tree.\n\nAn empty tree object is _unusual_.  Recent porcelains try reasonably hard\nnot to let the user create a commit that contains such a tree.  Perhaps\nwarning about them in git-fsck may have some merit.\n\nHOWEVER.\n\nBeing unusual and being errorneous are two quite different things.  This\nis especially true now we seem to use the same fsck_$object() code in\nplaces other than git-fsck itself.  For example, receive-pack should not\nreject unusual objects, even if it would be a good idea to tighten it to\nreject incorrect ones.\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6883d1bd68d158290acb18ae9b4e8baba7525201",
      "old_mode": 33188,
      "old_path": "fsck.c",
      "new_id": "797e3178ae279f444d2efa7e3758652ad0898dd7",
      "new_mode": 33188,
      "new_path": "fsck.c"
    }
  ]
}