)]}'
{
  "commit": "b3de3512f0276c7af73b3f2de0637c423d459f2e",
  "tree": "da3de6584a8d1442b079d081ee3a841b1a29802d",
  "parents": [
    "aef87f5214d4e8b5924281d82dae2c8156f4203a"
  ],
  "author": {
    "name": "Alex Vakulenko",
    "email": "avakulenko@google.com",
    "time": "Fri Dec 11 16:46:30 2015 -0800"
  },
  "committer": {
    "name": "Vitaly Buka",
    "email": "vitalybuka@google.com",
    "time": "Sat Dec 12 01:29:15 2015 +0000"
  },
  "message": "Fix device registration expiration with system clock adjusted\n\nWhen system clock is being adjusted on device during registration,\nthe registration process could prematurely be considered expired\nwhen the clock rolls forward. Change the logic to use retry counters\ninstead of absolute expiration time to mitigate this problem.\n\nBUG: 26107811\nChange-Id: I31de553bedabd7b501ed1d222932d4f379018dd2\nReviewed-on: https://weave-review.googlesource.com/1893\nReviewed-by: Vitaly Buka \u003cvitalybuka@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "170688b1d6ddfe3bbbc268e8ff9e3d54ccd5e6e1",
      "old_mode": 33188,
      "old_path": "src/privet/cloud_delegate.cc",
      "new_id": "1747f7cb3c4e338f35fa71eb4aee4d5f25cee235",
      "new_mode": 33188,
      "new_path": "src/privet/cloud_delegate.cc"
    }
  ]
}
