)]}'
{
  "commit": "bca01cd0bfdb9bfda3f076697bda4fae27d4e768",
  "tree": "78f5379af871823f3a45f04933561d0877853111",
  "parents": [
    "35c3afdb62809e40422b5590d807418697ba8660"
  ],
  "author": {
    "name": "Russ Cox",
    "email": "rsc@golang.org",
    "time": "Sun Jun 24 19:47:50 2012 -0400"
  },
  "committer": {
    "name": "Russ Cox",
    "email": "rsc@golang.org",
    "time": "Sun Jun 24 19:47:50 2012 -0400"
  },
  "message": "runtime: detect hash map collision problems\n\nThis can only happen if the hash function we\u0027re using is getting\nfar more than it\u0027s fair share of collisions, but that has happened\nto us repeatedly as we\u0027ve expanded the allowed use cases for\nhash tables (issue 1544, issue 2609, issue 2630, issue 2883, issue 3695).\nMaybe this will help the next time we try something new.\n\nR\u003dgolang-dev, r\nCC\u003dgolang-dev\nhttps://golang.org/cl/6306083\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ea9887a19fa6224c51cc361ff2f8e22618eba204",
      "old_mode": 33188,
      "old_path": "src/pkg/runtime/hashmap.c",
      "new_id": "e8965a68d5d026e6e6dae94f7d3100c12ae59bd8",
      "new_mode": 33188,
      "new_path": "src/pkg/runtime/hashmap.c"
    }
  ]
}
