)]}'
{
  "commit": "18b5d68c0d9f100954f899a295aa117c473de847",
  "tree": "57a075cdb459e96af4b694788e2ccf6b8a25f72d",
  "parents": [
    "bfa936696847cd7c1f01ba5fb790c40be72c9d97"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Wed Sep 13 15:52:01 2017 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Wed Sep 13 15:52:01 2017 +0300"
  },
  "message": "Fixed ngx_gmtime() on 32-bit platforms with 64-bit time_t.\n\nIn ngx_gmtime(), instead of casting to ngx_uint_t we now work with\ntime_t directly.  This allows using dates after 2038 on 32-bit platforms\nwhich use 64-bit time_t, notably NetBSD and OpenBSD.\n\nAs the code is not able to work with negative time_t values, argument\nis now set to 0 for negative values.  As a positive side effect, this\nresults in Epoch being used for such values instead of a date in distant\nfuture.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1e36675e360d5fa33459cf72c2f339d9cf790b73",
      "old_mode": 33188,
      "old_path": "src/core/ngx_times.c",
      "new_id": "ef63f1e3d199e86527a6aa878e9614e5ea416fe6",
      "new_mode": 33188,
      "new_path": "src/core/ngx_times.c"
    }
  ]
}
