)]}'
{
  "commit": "f366a9b007909cc6d214fbee26a97e880734a094",
  "tree": "868fb57fd51d7c03ffbedb56ee27db5146e2c3b2",
  "parents": [
    "e2978c8dcafdf20c2b49999ec423cb5f76d4a583"
  ],
  "author": {
    "name": "Brad Fitzpatrick",
    "email": "bradfitz@android.com",
    "time": "Tue Aug 24 16:14:07 2010 -0700"
  },
  "committer": {
    "name": "Brad Fitzpatrick",
    "email": "bradfitz@android.com",
    "time": "Tue Aug 24 18:07:33 2010 -0700"
  },
  "message": "Negatively cache settings and proactively slurp settings into cache.\n\nThe settings database cache is tiny (or should be tiny) and can be\nslurped into memory.  Once it\u0027s in memory and we know we have it all\nwe can avoid going to disk at all for keys not in the cache.\n\nThis is a big percentage of the StrictMode violations \u0026 latency.\n\nChange-Id: I649411be0c40d348f58376ccfb3eda059fd69fbc\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2e95932c292759792d711951c7132d5d00ffd90f",
      "old_mode": 33188,
      "old_path": "packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java",
      "new_id": "81d82dea6aef0cdb6eb35fdf1b0ec9605c756c24",
      "new_mode": 33188,
      "new_path": "packages/SettingsProvider/src/com/android/providers/settings/SettingsProvider.java"
    }
  ]
}