)]}'
{
  "commit": "4d75f2aea776f434b51481ae65233d6012da1a66",
  "tree": "98d0fd5f779697e72b6370adcffd8510e33bef24",
  "parents": [
    "e85ae279b0d58edc2f4c3fd5ac391b51e1223985"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Dec 12 21:54:14 2025 +0900"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Dec 12 22:05:19 2025 +0900"
  },
  "message": "FLEX_ARRAY: require platforms to support the C99 syntax\n\nBefore C99 syntax to express that the final member in a struct is an\narray of unknown number of elements, i.e.,\n\n\tstruct {\n\t\t...\n\t\tT flexible_array[];\n\t};\n\ncame along, GNU introduced their own extension to declare such a\nmember with 0 size, i.e.,\n\n\t\tT flexible_array[0];\n\nand the compilers that did not understand even that were given a way\nto emulate it by wasting one element, i.e.,\n\n\t\tT flexible_array[1];\n\nAs we are using more and more C99 language features, let\u0027s see if\nthe platforms that still need to resort to the historical forms of\nflexible array member support are still there, by forcing all the\nflex array definitions to use the C99 syntax and see if anybody\nscreams (in which case reverting the changes is rather easy).\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "398e0fac4fab6007903fdd9fd31dcc28fe531a65",
      "old_mode": 33188,
      "old_path": "git-compat-util.h",
      "new_id": "8010397bdb5b805f3374b1797fceb01e0b1271b9",
      "new_mode": 33188,
      "new_path": "git-compat-util.h"
    }
  ]
}