)]}'
{
  "commit": "d572a13021b0430eddf83e9caedc9d5add693c62",
  "tree": "a0dfe1a74aded3d9266eef72ee9ceec4cc9ef5a4",
  "parents": [
    "3ba5f95b46f06ed3d7382346de29ac550d749ec9"
  ],
  "author": {
    "name": "Victor Boivie",
    "email": "victor.boivie@sonyericsson.com",
    "time": "Thu Nov 11 20:36:39 2010 +0100"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Thu Apr 07 17:19:06 2011 -0400"
  },
  "message": "Added repo cherry-pick command\n\nIt is undesired to have the same Change-Id:-line for two separate\ncommits, and when cherry-picking, the user must manually change it.\n\nIf this is not done, bad things may happen (such as when the user\nis uploading the cherry-picked commit to Gerrit, it will instead\nsee it as a new patch-set for the original change, or worse).\n\nrepo cherry-pick works the same was as git cherry-pick, except that\nit replaces the Change-Id with a new one and adds a reference\nback to the commit from where it was picked.\n\nOn failures (when git can not successfully apply the cherry-picked\ncommit), instructions will be written to the user.\n\nChange-Id: I5a38b89839f91848fad43386d43cae2f6cdabf83\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "8da3a75044994a2f0969dd13772ca52877f11615",
      "new_mode": 33188,
      "new_path": "subcmds/cherry_pick.py"
    }
  ]
}