)]}'
{
  "log": [
    {
      "commit": "79192ca8ebd9a25c583aa46024a250fef1e7766f",
      "tree": "e84e8eb7e9fe7b8566671952850570461729d08f",
      "parents": [
        "0a830dad5e3ceffc1f12f3e674322182d809e3a9"
      ],
      "author": {
        "name": "Jason Cooper",
        "email": "jason@lakedaemon.net",
        "time": "Mon Apr 07 18:30:29 2014 +0000"
      },
      "committer": {
        "name": "Michal Marek",
        "email": "mmarek@suse.cz",
        "time": "Tue Apr 08 16:41:44 2014 +0200"
      },
      "message": "scripts: objdiff: detect object code changes between two commits\n\nobjdiff is useful when doing large code cleanups.  For example, when\nremoving checkpatch warnings and errors from new drivers in the staging\ntree.\n\nobjdiff can be used in conjunction with a git rebase to confirm that\neach commit made no changes to the resulting object code.  It has the\nsame return values as diff(1).\n\nThis was written specifically to support adding the skein and threefish\ncryto drivers to the staging tree.  I needed a programmatic way to\nconfirm that commits changing \u003e90% of the lines didn\u0027t inadvertently\nchange the code.\n\nTemporary files (objdump output) are stored in\n\n  /path/to/linux/.tmp_objdiff\n\n\u0027make mrproper\u0027 will remove this directory.\n\nSigned-off-by: Jason Cooper \u003cjason@lakedaemon.net\u003e\nSigned-off-by: Michal Marek \u003cmmarek@suse.cz\u003e\n"
    }
  ]
}