)]}'
{
  "commit": "e8f75fa3687bfe894a4fa8e59881b7d9170d8a41",
  "tree": "e43b915e9336ddfad189c3855107831300a47257",
  "parents": [
    "87636f2ac2d8a10e7db3be7b5dd47097cc1084ce"
  ],
  "author": {
    "name": "Torne (Richard Coles)",
    "email": "torne@google.com",
    "time": "Fri Jul 20 15:32:19 2012 +0100"
  },
  "committer": {
    "name": "Torne (Richard Coles)",
    "email": "torne@google.com",
    "time": "Fri Jul 20 15:33:17 2012 +0100"
  },
  "message": "Don\u0027t delete the branch config when switching branches.\n\nThe fix for issue #46 in 5d016502ebc6 appears to break syncing in some\nsituations: the branch is deleted after the point where it\u0027s been\nconfigured, which deletes part of its configuration and causes the\nconfig to change each time you call `repo init`, alternating between a\nconfiguration that works and one that doesn\u0027t.\n\nInstead of deleting the branch with git branch -D, use git update-ref -d\nwhich just deletes the ref (to avoid the rebase) without touching the\nconfiguration for the branch that was set up during the first repo init.\n\nThis appears to ensure the config is left in a valid state all the time\nno matter what combination of repo init commands you run, without\nreintroducing the rebasing issue.\n\nChange-Id: Iaadaa6e56a46840bbc593fa5b35cb5b34cd3ce69\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "114ff491705fe0636b819ea1b62be145b39c958a",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "66a123d258ae8215720b1a0c9e9f1709f84c7931",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}