)]}'
{
  "commit": "5e57234ec619d0de930333a8dde3004d1dc575d6",
  "tree": "40f4eab3f13e5b4a1ca4ff3f501539ae63f44229",
  "parents": [
    "5d016502ebc68bc054d85c98c6cdb51e0b63a1f5"
  ],
  "author": {
    "name": "Joe Hansche",
    "email": "jhansche@myyearbook.com",
    "time": "Mon Mar 05 11:41:19 2012 -0500"
  },
  "committer": {
    "name": "Shawn O. Pearce",
    "email": "sop@google.com",
    "time": "Wed Jun 13 10:34:41 2012 -0700"
  },
  "message": "Support automatically stashing local modifications during repo-rebase.\n\nCurrently repo-rebase requires that all modifications be committed\nlocally before it will allow the rebase. In high-velocity environments,\nyou may want to just pull in newer code without explicitly creating\nlocal commits, which is typically achieved using git-stash.\n\nIf called with the --auto-stash command line argument, and it is\ndetermined that the current index is dirty, the local modifications\nare stashed, and the rebase continues.  If a stash was performed, that\nstash is popped once the rebase completes.\n\nNote that there is still a possibility that the git-stash pop will\nresult in a merge conflict.\n\nChange-Id: Ibe3da96f0b4486cb7ce8d040639187e26501f6af\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7c8e9389138f6f839c510a0c89b4f1b834ee47cc",
      "old_mode": 33188,
      "old_path": "subcmds/rebase.py",
      "new_id": "20662b11aed33680f77fcc64bf4b735b0667386d",
      "new_mode": 33188,
      "new_path": "subcmds/rebase.py"
    }
  ]
}