)]}'
{
  "commit": "224c7d70fa14ed44d8e7e3ce1e165e05b7b23725",
  "tree": "491c48053c5501c28fb3907f5cc1b224c89dcf18",
  "parents": [
    "53a06cf39b756eddfe4a2a34da93e3d04eb7b728"
  ],
  "author": {
    "name": "Johannes Schindelin",
    "email": "johannes.schindelin@gmx.de",
    "time": "Tue Dec 31 22:53:50 2019 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Jan 02 12:56:08 2020 -0800"
  },
  "message": "mingw: only test index entries for backslashes, not tree entries\n\nDuring a clone of a repository that contained a file with a backslash in\nits name in the past, as of v2.24.1(2), Git for Windows prints errors\nlike this:\n\n\terror: filename in tree entry contains backslash: \u0027\\\u0027\n\nThe idea is to prevent Git from even trying to write files with\nbackslashes in their file names: while these characters are valid in\nfile names on other platforms, on Windows it is interpreted as directory\nseparator (which would obviously lead to ambiguities, e.g. when there is\na file `a\\b` and there is also a file `a/b`).\n\nArguably, this is the wrong layer for that error: As long as the user\nnever checks out the files whose names contain backslashes, there should\nnot be any problem in the first place.\n\nSo let\u0027s loosen the requirements: we now leave tree entries with\nbackslashes in their file names alone, but we do require any entries\nthat are added to the Git index to contain no backslashes on Windows.\n\nNote: just as before, the check is guarded by `core.protectNTFS` (to\nallow overriding the check by toggling that config setting), and it\nis _only_ performed on Windows, as the backslash is not a directory\nseparator elsewhere, even when writing to NTFS-formatted volumes.\n\nAn alternative approach would be to try to prevent creating files with\nbackslashes in their file names. However, that comes with its own set of\nproblems. For example, `git config -f C:\\ProgramData\\Git\\config ...` is\na very valid way to specify a custom config location, and we obviously\ndo _not_ want to prevent that. Therefore, the approach chosen in this\npatch would appear to be better.\n\nThis addresses https://github.com/git-for-windows/git/issues/2435\n\nSigned-off-by: Johannes Schindelin \u003cjohannes.schindelin@gmx.de\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fc80d7982b81bf06d1fc029e443ffc30a3aef9bf",
      "old_mode": 33188,
      "old_path": "read-cache.c",
      "new_id": "5baf652a5476946b1c56dc59d262d51b6dd8fa59",
      "new_mode": 33188,
      "new_path": "read-cache.c"
    },
    {
      "type": "modify",
      "old_id": "905a557585afdbf2c0774e804067129058a7ef82",
      "old_mode": 33261,
      "old_path": "t/t7415-submodule-names.sh",
      "new_id": "7ae0dc8ff47ee763089284784e6acdbbdbdb4625",
      "new_mode": 33261,
      "new_path": "t/t7415-submodule-names.sh"
    },
    {
      "type": "modify",
      "old_id": "31cec2a08dc6a4490de525c7f31819a98a38e186",
      "old_mode": 33188,
      "old_path": "tree-walk.c",
      "new_id": "bea819d826fb1c855a7b92dbe2605885c12f5c16",
      "new_mode": 33188,
      "new_path": "tree-walk.c"
    }
  ]
}