)]}'
{
  "commit": "edeeef2aadd9e2f4109dec3f624aafea60cee9bb",
  "tree": "b25a8dab6192fe6bf382811017a66b310f2dfe7f",
  "parents": [
    "df6c08b9ffe49fc5501cdded0e3da832b0921bf6"
  ],
  "author": {
    "name": "Liu Hao",
    "email": "lh_mouse@126.com",
    "time": "Wed Jul 22 22:19:01 2020 +0800"
  },
  "committer": {
    "name": "Liu Hao",
    "email": "lh_mouse@126.com",
    "time": "Wed Jul 22 22:19:01 2020 +0800"
  },
  "message": "crt/stdio/fseeki64: Copy-n-paste from `f{tell,seek}o64()`\n\nThe old implementation of `_ftelli64()` was introduced in 518dd33c326 in\n2007. However it sometimes reports incorrect values. This program, after\nbeing compiled with `i686-w64-mingw32-gcc`, outputs `-15` on the second\nline on my Windows 7 Professional:\n\n    #include \u003cstdio.h\u003e\n    #include \u003cassert.h\u003e\n\n    int main(void)\n      {\n        FILE* fp \u003d fopen(__FILE__, \"rb\");\n        assert(fp);\n        printf(\"offset \u003d %lld\\n\", (long long)_ftelli64(fp));\n\n        char buf[1];\n        ssize_t nread \u003d fread(\u0026buf, 1, 1, fp);\n        assert(nread \u003d\u003d 1);\n        printf(\"offset \u003d %lld\\n\", (long long)_ftelli64(fp));\n\n        fclose(fp);\n      }\n\nThis is apparently incorrect, as file offsets can\u0027t be negative.\n\nIf it was compiled with `x86_64-w64-mingw32-gcc`, it however outputs `1`\nas expected.\n\nSince 4d3b28a992, we have had 64-bit tell/seek functions. They should be\nused to de-duplicate these implementations.\n\nSigned-off-by: Liu Hao \u003clh_mouse@126.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fdb8f1c19b2439997e579419f68863d07058e69d",
      "old_mode": 33188,
      "old_path": "mingw-w64-crt/stdio/fseeki64.c",
      "new_id": "f70062e3911805f8d3dcaecccff541ebd34bf023",
      "new_mode": 33188,
      "new_path": "mingw-w64-crt/stdio/fseeki64.c"
    }
  ]
}