)]}'
{
  "log": [
    {
      "commit": "2c72b6822debb08fe997926eedc110f62d287d34",
      "tree": "467e1c3b5b131a3d2991f9d6597fc2d3371a94ab",
      "parents": [
        "921ec8056a3010d0a21400f97312cf3f7d97ffaa"
      ],
      "author": {
        "name": "Adam Lesinski",
        "email": "adamlesinski@google.com",
        "time": "Tue Jun 24 09:56:01 2014 -0700"
      },
      "committer": {
        "name": "Adam Lesinski",
        "email": "adamlesinski@google.com",
        "time": "Wed Jul 23 14:11:46 2014 -0700"
      },
      "message": "Add \u003cfeature-group\u003e tag and change aapt badging\n\nA \u003cfeature-group\u003e represents a set of features required\nfor an app to be compatible with a device. Multiple\n\u003cfeature-group\u003e elements represent a logical \u0027or\u0027\nof required features.\n\nFeatures defined in the old way with \u003cuses-feature\u003e tags\nunder the \u003cmanifest\u003e tag are automatically added to each\nfeature-group defined.\n\nDefining a \u003cfeature-group\u003e means that any default\nfeatures are not included (such as android.hardware.touchscreen)\nand declared permissions do not imply any features.\n\nChange-Id: I45626f0fdc546e47bcf2aead7ef05ebcca12b023\n"
    }
  ]
}