)]}'
{
  "log": [
    {
      "commit": "13e2fda38720cebf4440ba361c2bbb8241dc6f4a",
      "tree": "c7b743940d9b9c328a20f5aaeaf7a100a3cf6773",
      "parents": [
        "2ca3dd3338d861ad844306c6efdbc57510671dfe"
      ],
      "author": {
        "name": "Steven Moreland",
        "email": "smoreland@google.com",
        "time": "Fri Jul 14 10:38:40 2017 -0700"
      },
      "committer": {
        "name": "Steven Moreland",
        "email": "smoreland@google.com",
        "time": "Fri Jul 14 10:38:40 2017 -0700"
      },
      "message": "Make libeffects build with the VNDK.\n\nWhen the vndk is enabled (BOARD_VNDK_VERSION\u003dcurrent),\nvendor libraries must only link against vendor variants\nin the build system. This also means that they receive\nrestricted sets of headers and that automatic global\nheaders are restricted.\n\nTest: build libeffects with BOARD_VNDK_VERSION\u003dcurrent\nBug: 37342627\nChange-Id: I95b4bc39eb98b5af4069ab64d81574a451c8131f\n"
    },
    {
      "commit": "42aa39a2c6864eeea8e40bd57230ff99ea71be5f",
      "tree": "c328f688309e95b2a662ad204ac579650fe948df",
      "parents": [
        "97b544846bd781afdbae55a28025020cb5772ec2"
      ],
      "author": {
        "name": "Kevin Rocard",
        "email": "krocard@google.com",
        "time": "Fri Jun 09 19:22:43 2017 -0700"
      },
      "committer": {
        "name": "Mikhail Naganov",
        "email": "mnaganov@google.com",
        "time": "Fri Jul 07 17:20:47 2017 -0700"
      },
      "message": "Effects config: Parse new configuration format\n\nFor treble, files shared between vendor and system must have a schema.\nAs .conf did not support such feature, transition to an xml based\nconfiguration file.\n\nThis new format has several changes:\n - library path are now relative to the standard effect directories\n - effect parameters are no longer supported (nobody used them)\n\nTest: Check that the dumpsys is similar than with the legacy formal\nBug: 37492580\nChange-Id: I333db2977280e2e0078815b88affd4ab9b01b8bc\nSigned-off-by: Kevin Rocard \u003ckrocard@google.com\u003e\n"
    }
  ]
}