)]}'
{
  "log": [
    {
      "commit": "bc73ffc06fd2b5b30802cc7e8874a986626b897d",
      "tree": "10a446a0a7f4eaf813aee1e4a7186c140fbcae34",
      "parents": [
        "5144d154b5bdea65000d349fee958a303083aa99"
      ],
      "author": {
        "name": "Felipe Leme",
        "email": "felipeal@google.com",
        "time": "Fri Dec 11 15:07:14 2015 -0800"
      },
      "committer": {
        "name": "Felipe Leme",
        "email": "felipeal@google.com",
        "time": "Wed Dec 16 11:36:04 2015 -0800"
      },
      "message": "Allows users to add details about a bugreport in progress.\n\nThe \"bugreport in progress\" notification now have a \"DETAILS\" button\nthat when clicked opens a dialog window displaying the following fields:\n\n  - Name: short name for the bugreport, will be used as part of the\n    final files (and by default is the timestamp sent by dumpstate)\n  - Title: a 1-line title for the bugreport, will be used as the subject\n    in the final message.\n  - Description: a detailed description for the bug.\n\nThe main advantage of such dialog is that it allows users to enter more\ninfo about a bugreport while it\u0027s being generated, rather then when the\nbugreport is finished (since of the user doesn\u0027t remember what the\ncontext was when the problem happened).\n\nBUG: 25794470\nBUG: 10676443\nChange-Id: I0d1dba2a94ad989e541415a2a59475619a2e3d13\n"
    },
    {
      "commit": "e53e85f6051d20cbd477bc25d446a41996411fab",
      "tree": "e007334a9b891f0a22c77b25c25904abb54232c9",
      "parents": [
        "12262af418f139e189b09b5b1e8a775d41d42e8e"
      ],
      "author": {
        "name": "Felipe Leme",
        "email": "felipeal@google.com",
        "time": "Tue Nov 17 17:37:53 2015 -0800"
      },
      "committer": {
        "name": "Felipe Leme",
        "email": "felipeal@google.com",
        "time": "Fri Nov 20 12:00:17 2015 -0800"
      },
      "message": "Initial integration test for BugReportReceiver.\n\nThese tests rely in the UI Automator to interact with the UI and\nfollow the workflow below:\n\n * creates the bug report files\n * generates the BUGREPORT_FINISHED intent\n * emulate user actions to share the intent with a custom activity\n * asserts the extras received by the custom activity\n\nIt still have some limitations, like requiring the phone to be unlocked\nand having the bugreport warning already checked, and those will be\naddressed in future CLs.\n\nBUG: 25752530\nChange-Id: I01d7fad9f94daf156b728cbb9ef228bbfa6ee0f5\n"
    }
  ]
}