)]}'
{
  "commit": "d16c34fb4ae3bc5433ec5364e2757c227d4ca39c",
  "tree": "7870e6ebe8d39d99a8bdda24a802051e638baae6",
  "parents": [
    "4d84182acc6c41b36ff729417c6770fbe2f55ca7"
  ],
  "author": {
    "name": "Keir Mierle",
    "email": "mierle@gmail.com",
    "time": "Fri Aug 10 16:44:44 2012 -0700"
  },
  "committer": {
    "name": "Keir Mierle",
    "email": "mierle@gmail.com",
    "time": "Fri Aug 10 16:44:52 2012 -0700"
  },
  "message": "Explicitly import string into the Ceres namespace.\n\nThis is a workaround for anyone building Ceres in an environment\nwhere there is a non-standard string implementation in the global\nnamespace. Due to the way the standard is written, a \"using\nnamespace X\" import is not high enough precedence to resolve a\nnaked reference to \"string\". Instead, by explicitly importing\nstring, the lookup becomes unambiguous.\n\nChange-Id: I8d70463de01c482796c5bc09da05b37d21e7af96\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9a3e5cced5866187616ad258db4b470e52fad864",
      "old_mode": 33188,
      "old_path": "include/ceres/internal/port.h",
      "new_id": "a9fe247cef5c44ff9f63b1bffe1761bddd2110fe",
      "new_mode": 33188,
      "new_path": "include/ceres/internal/port.h"
    }
  ]
}