)]}'
{
  "log": [
    {
      "commit": "569ca8b7dd6931d21babb94839dc6029b9c652df",
      "tree": "077dc5f9fb46207cede7613a521c0d969b2193ce",
      "parents": [
        "561ff8a74e3d9ea15f58d9b6534da9ea5a63d84b"
      ],
      "author": {
        "name": "Justin Ho",
        "email": "justinho@google.com",
        "time": "Fri Jun 01 14:07:23 2012 -0700"
      },
      "committer": {
        "name": "Justin Ho",
        "email": "justinho@google.com",
        "time": "Fri Jun 01 14:09:26 2012 -0700"
      },
      "message": "Temporarily disable FakeOemFeatures from userdebug or higher builds\n\nChange-Id: I452d079f60a087a36c20e984b38b8354327e1d5a\n"
    },
    {
      "commit": "04a3a4350e320b65bda9fae6500250c4880e4bf2",
      "tree": "1c8b8a2806c111c4705999a135bd96d9a980e998",
      "parents": [
        "2437a4ab02d0adcbb0c4c762210762db2973cce8"
      ],
      "author": {
        "name": "Ying Wang",
        "email": "wangying@google.com",
        "time": "Tue Feb 28 12:53:19 2012 -0800"
      },
      "committer": {
        "name": "Ying Wang",
        "email": "wangying@google.com",
        "time": "Tue Feb 28 12:53:19 2012 -0800"
      },
      "message": "Disable ProGuard for FakeOemFeatures to fix build.\n\nChange-Id: If0ccf16712bf43adb5fe490906be2a13b484f726\n"
    },
    {
      "commit": "d459f4bbfcfe4989a0e2298b3cfd36064b386b88",
      "tree": "2daf1a933af25393ef94b5d086cacb92aef1bf47",
      "parents": [
        "35ae6e2a841d8a287bccb56881f58e9fe24a07b6"
      ],
      "author": {
        "name": "Dianne Hackborn",
        "email": "hackbod@google.com",
        "time": "Mon Feb 27 18:37:40 2012 -0800"
      },
      "committer": {
        "name": "Dianne Hackborn",
        "email": "hackbod@google.com",
        "time": "Mon Feb 27 18:46:29 2012 -0800"
      },
      "message": "You could think of this as what an OEM might do.\n\nExcept it does nothing.\n\nBut eat resources.\n\nYum, yum!\n\nCurrent we create five processes.  The main process sucks up 16MB of\nRAM and creates a full-screen window; only on high-end devices does\nthe window (and process) use the GPU.\n\nThe second through fourth processes just sits there not really doing\nanything except using process overhead.\n\nThe fifth process runs a background service, slowing eating RAM until\nit gets killed by the system (as the system will ultimately do with\nbackground services).  It also creates a full-screen window, and always\nuses the GPU even on low-end devices.\n\nChange-Id: Ibe9e25f7dbd889f4dc83eed6a3c09b9b0437b4e3\n"
    }
  ]
}