)]}'
{
  "commit": "752b9b34f5e71151145a8d396fa8b4b7178eba40",
  "tree": "9a0243ad63928493fcd9bb19a47419b8e1a11727",
  "parents": [
    "6d69d502a7560249a619bec56d3a946ec7fe934c"
  ],
  "author": {
    "name": "J. Richard Barnette",
    "email": "jrbarnette@chromium.org",
    "time": "Thu Feb 16 16:07:18 2012 -0800"
  },
  "committer": {
    "name": "Richard Barnette",
    "email": "jrbarnette@chromium.org",
    "time": "Tue Feb 21 14:05:40 2012 -0800"
  },
  "message": "cros_generate_update_payload: Delete -d options from umount\n\nThe -d option to umount is unnecessary in cases where the original\nmount was created with \u0027-o loop\u0027 (it says so in the man page).\nMoreover, there\u0027s a demonstrable bug when using \u0027umount -d\u0027 in this\ncase:  umount complains that it\u0027s unable to delete the loop device\nin this case.  This change silences those messages.\n\nThe demonstrated bug in umount is a plausible explanation for build\nfailures characterized by unexpected failures of \u0027mount -o loop\u0027;\nsee the BUG, below.\n\nBUG\u003dchromium-os:24975\nTEST\u003dTBD\n\nChange-Id: I8f3b3274ccea3dd5a5b35e880bbe220846061d3a\nReviewed-on: https://gerrit.chromium.org/gerrit/16186\nReviewed-by: David James \u003cdavidjames@chromium.org\u003e\nTested-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "edbf303c4d1f17b268ffeb1cbf1ee7ae27448107",
      "old_mode": 33261,
      "old_path": "host/cros_generate_update_payload",
      "new_id": "e2fdcd3cb931c8320f1d7f5c5a36d6ed98ea50a5",
      "new_mode": 33261,
      "new_path": "host/cros_generate_update_payload"
    }
  ]
}