)]}'
{
  "commit": "c159e38d756c9c46493ea8f07bd3c8bffeb5ce7e",
  "tree": "3bd57b8415dd7d30923e87e57ba4ef666db15fea",
  "parents": [
    "b6089f03e107d5427fce44279634f229301462f3"
  ],
  "author": {
    "name": "Simon Glass",
    "email": "sjg@chromium.org",
    "time": "Mon Aug 05 19:42:04 2013 -0600"
  },
  "committer": {
    "name": "ChromeBot",
    "email": "chrome-bot@google.com",
    "time": "Sat Aug 10 20:26:34 2013 -0700"
  },
  "message": "cros_bundle_firmware: Ensure the flasher avoids silent/bootsecure\n\nThese options need to be disabled for the flasher. We don\u0027t want a silent\nconsole since then it is impossible to see when the flasher finishes. We\ndon\u0027t want bootsecure since then the flasher script cannot run.\n\nA previous interim change corrected the \u0027silent\u0027 flag - the change completes\nthe fix and will allow us to make an image self-flashing in a later change\n(i.e. we pull out U-Boot and the FDT from the image to be flashed, and use\nthose to flash it).\n\nBUG\u003dchrome-os-partner:21115\nTEST\u003dFEATURES\u003dtest sudo -E  emerge cros-devutils\nFlash U-Boot with \u0027crosfw -b peach_pit -SCF\u0027\n\n -C means silent console\n -S means bootsecure\n\nSee that we still get messages from the flasher, and it succeeds in its task.\n\nChange-Id: I7a96a041ffbab6dfae4adcf6827fa39e925c9fb7\nSigned-off-by: Simon Glass \u003csjg@chromium.org\u003e\nReviewed-on: https://gerrit.chromium.org/gerrit/64742\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4f2af1d56959d8e7d5071fc13c7058b710fa3955",
      "old_mode": 33188,
      "old_path": "host/lib/write_firmware.py",
      "new_id": "8624a6a7afa9c4f5b05b523d02a6e0c080c1285e",
      "new_mode": 33188,
      "new_path": "host/lib/write_firmware.py"
    }
  ]
}