)]}'
{
  "commit": "83b08eb19f05710a92d565124606dcaf68bcc68b",
  "tree": "9455e55d98f5fb3a68e46571a58d055956881617",
  "parents": [
    "7e6073d27083054773f3c3b21a608f400cf7348d"
  ],
  "author": {
    "name": "Patrick Steinhardt",
    "email": "ps@pks.im",
    "time": "Wed Oct 09 15:25:18 2024 +0200"
  },
  "committer": {
    "name": "Johannes Schindelin",
    "email": "johannes.schindelin@gmx.de",
    "time": "Wed Oct 30 17:38:35 2024 +0100"
  },
  "message": "t7300: work around platform-specific behaviour with long paths on MinGW\n\nWindows by default has a restriction in place to only allow paths up to\n260 characters. This restriction can nowadays be lifted by setting a\nregistry key, but is still active by default.\n\nIn t7300 we have one test that exercises the behaviour of git-clean(1)\nwith such long paths. Interestingly enough, this test fails on my system\nthat uses Windows 10 with mingw-w64 installed via MSYS2: instead of\nobserving ENAMETOOLONG, we observe ENOENT. This behaviour is consistent\nacross multiple different environments I have tried.\n\nI cannot say why exactly we observe a different error here, but I would\nnot be surprised if this was either dependent on the Windows version,\nthe version of MinGW, the current working directory of Git or any kind\nof combination of these.\n\nWork around the issue by handling both errors.\n\n[Backported from 106834e34a2 (t7300: work around platform-specific\nbehaviour with long paths on MinGW, 2024-10-09).]\n\nSigned-off-by: Patrick Steinhardt \u003cps@pks.im\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\nSigned-off-by: Johannes Schindelin \u003cjohannes.schindelin@gmx.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c975eb54d234d77b2f13df2a96acd4cbefb93865",
      "old_mode": 33261,
      "old_path": "t/t7300-clean.sh",
      "new_id": "a831438f74221be105fb76054ed926e16d4075aa",
      "new_mode": 33261,
      "new_path": "t/t7300-clean.sh"
    }
  ]
}