)]}'
{
  "commit": "bdb866ea7630b1aecad0ddc7d72939e67ff39816",
  "tree": "73dd76e6cc3753783e95c5de50e08d4a27485996",
  "parents": [
    "e121ad558dac2268bba4eb37528ec5a6a2aa507d"
  ],
  "author": {
    "name": "Dan Willemsen",
    "email": "dwillemsen@google.com",
    "time": "Tue Apr 05 17:22:02 2016 -0700"
  },
  "committer": {
    "name": "Dan Willemsen",
    "email": "dwillemsen@google.com",
    "time": "Tue Apr 05 17:44:09 2016 -0700"
  },
  "message": "Fix symlinking of new projects\n\nWe weren\u0027t copying these lists, so the +\u003d was actually changing the\nunderlying lists.\n\nWhen a new project was added to the manifest, we run _CheckDirReference\nagainst the manifest project with share_refs\u003dTrue, which added the\nworking_tree_* to the shareable_* lists. Then, when we load the new\nmanifest and create the new project, it uses the lists that already\ncontain the working_tree_* files, even though we passed\nshare_refs\u003dFalse.\n\nThis happens reliably under the above conditions, but doesn\u0027t seem to\nhappen when syncing a fresh tree. So we\u0027ve got a mixture of links that\nmay need to be cleaned up later. This patch will just stop it from\nhappening in the future.\n\nChange-Id: Ib7935bfad78af1e494a75e55134ec829f13c2a41\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e3c3bd51735e58323bf63bde12c971c4800d9bb8",
      "old_mode": 33188,
      "old_path": "project.py",
      "new_id": "e0bd9c10ff66706b01e539aae9e48d62578bdf07",
      "new_mode": 33188,
      "new_path": "project.py"
    }
  ]
}