)]}'
{
  "commit": "666d534636d262cbfd971509dd0f0be0cddb2e11",
  "tree": "f7341695337a3179d7c77c5fb1272d6e4f83f595",
  "parents": [
    "f2af7564256a65221e0ebc45d716672a42cd537a"
  ],
  "author": {
    "name": "Conley Owens",
    "email": "cco3@android.com",
    "time": "Thu May 01 13:09:57 2014 -0700"
  },
  "committer": {
    "name": "Conley Owens",
    "email": "cco3@android.com",
    "time": "Thu May 01 13:20:32 2014 -0700"
  },
  "message": "Ensure HEAD is correct when skipping remote fetch\n\nA recent optimization (2fb6466f795eb30c1dfa598501f5b5d2981e6a5f) skips\nperforming a remote fetch if we already know we have the sha1 we want.\nHowever, that optimization skipped initialization steps that ensure HEAD\npoints to the correct sha1.  This change makes sure not to skip those\nsteps.\n\nHere is an example of how to test this change:\n\n\"\"\"\"\"\"\"\"\"\nurl\u003d\u003cmanifest url\u003e\nbranch1\u003d\u003cbranch name\u003e\nbranch2\u003d\u003cbranch name\u003e\nproject\u003d\u003cproject with revision set to different sha1 in each branch\u003e\n\nrepo init -u $url -b $branch1 --mirror\nrepo sync $project\nfirst\u003d$(cd $project.git; git rev-parse HEAD)\n\nrepo init -b $branch2\nrepo sync $project\nsecond\u003d$(cd platform/build.git; git rev-parse HEAD)\n\nif [[ $first \u003d\u003d $second ]]\nthen\n    echo \u0027problem!\u0027\nelse\n    echo \u0027no problem!\u0027\nfi\n\"\"\"\"\"\"\"\"\"\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "22184578e649d547ae327ea7183304cf136821c5",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "127176e54b6c5f38c3ebc258947a493c4de3df8a",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}