)]}'
{
  "commit": "3a7f0908b6d698ab1287840ea604111c28a67a61",
  "tree": "163ecada89691962d93c8bd1a30710c2a4055c88",
  "parents": [
    "6ff7f460394745395f3eec1e414ad2300c6a402f"
  ],
  "author": {
    "name": "Matheus Tavares",
    "email": "matheus.bernardino@usp.br",
    "time": "Thu May 06 16:33:15 2021 -0300"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri May 07 07:48:11 2021 +0900"
  },
  "message": "clean: remove unnecessary variable\n\nThe variable `matches` used to hold the return of a `dir_path_match()`\ncall that was removed in 95c11ecc73 (\"Fix error-prone fill_directory()\nAPI; make it only return matches\", 2020-04-01). Now `matches` will\nalways hold 0, which is the value it\u0027s initialized with; and the\ncondition `matches !\u003d MATCHED_EXACTLY` will always evaluate to true. So\nlet\u0027s remove this unnecessary variable.\n\nInterestingly, it seems that `matches !\u003d MATCHED_EXACTLY` was already\nunnecessary before 95c11ecc73. That\u0027s because `remove_directories` is\nalways set to 1 when we have pathspecs; So, in the condition\n`!remove_directories \u0026\u0026 matches !\u003d MATCHED_EXACTLY`, we would either:\n\n- have pathspecs (or have been given `-d`) and ignore `matches` because\n  `remove_directories` is 1; or\n\n- not have pathspecs (nor `-d`) and end up just checking that\n  `0 !\u003d MATCHED_EXACTLY`, as `matches` would never get reassigned\n  after its zero initialization (because there is no pathspec to match).\n\nSigned-off-by: Matheus Tavares \u003cmatheus.bernardino@usp.br\u003e\nReviewed-by: Elijah Newren \u003cnewren@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ca12bc0c0ba2c3bc3084a320835cf83600173ce",
      "old_mode": 33188,
      "old_path": "builtin/clean.c",
      "new_id": "e3046b962c1d0604558c11b39b093b04069cb371",
      "new_mode": 33188,
      "new_path": "builtin/clean.c"
    }
  ]
}