)]}'
{
  "commit": "d2ee3ca7c190879d5262b6b00aa77fb93786b292",
  "tree": "5c3645003e9d7f0c6874b70af08775494f61d4d8",
  "parents": [
    "bbd5c6e9e59e8a897b04f56a91cf6be4902fb1c4"
  ],
  "author": {
    "name": "C Shapiro",
    "email": "shapiroc@chromium.org",
    "time": "Tue Aug 29 11:36:03 2017 -0600"
  },
  "committer": {
    "name": "chrome-bot",
    "email": "chrome-bot@chromium.org",
    "time": "Wed Aug 30 13:04:21 2017 -0700"
  },
  "message": "image_signing: Don\u0027t create empty keyset subdir\n\nupdater4.sh uses the /keyset subdir from the firmware updater shellball\nto indicate if it should use model specific keys or not.  This won\u0027t\nwork for any case where the signers haven\u0027t been updated with model\nspecific keys yet.\n\nChanged the output for unibuilds to be consistent with non-uni builds\nwhere the /keyset subdir won\u0027t be created if loem.ini doesn\u0027t exist on\nthe signer.\n\nBUG\u003db:65128657\nTEST\u003dcrrev.com/c/626718 and crrev.com/c/636344 test cases, which cover\nboth the shared and non-shared key use cases\nBRANCH\u003dNone\n\nChange-Id: I38db1385fa99ac4a9843a750c336c58b74b127b4\nReviewed-on: https://chromium-review.googlesource.com/642031\nCommit-Ready: Simon Glass \u003csjg@chromium.org\u003e\nTested-by: Simon Glass \u003csjg@chromium.org\u003e\nTested-by: C Shapiro \u003cshapiroc@google.com\u003e\nReviewed-by: Simon Glass \u003csjg@chromium.org\u003e\nReviewed-by: Jason Clinton \u003cjclinton@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d56c15690f64c61ff3fa0c2c793c8a9e95caab6b",
      "old_mode": 33261,
      "old_path": "scripts/image_signing/sign_official_build.sh",
      "new_id": "e4426af17f978ab2cfe0c172820292648ed4666f",
      "new_mode": 33261,
      "new_path": "scripts/image_signing/sign_official_build.sh"
    }
  ]
}