)]}'
{
  "commit": "1f5653358813e2dc2656910d2de7ed9d355bad3f",
  "tree": "a730341c708db7ff2ef5020b858dabc871412758",
  "parents": [
    "f404f0059d71c8c86da7b56c48794266b5befd10"
  ],
  "author": {
    "name": "Bruce Dawson",
    "email": "brucedawson@chromium.org",
    "time": "Wed Feb 16 13:56:26 2022 -1000"
  },
  "committer": {
    "name": "Bruce Dawson",
    "email": "brucedawson@chromium.org",
    "time": "Wed Feb 16 14:03:04 2022 -1000"
  },
  "message": "Don\u0027t disable stdout buffering on Windows\n\nLong ago ninja disabled stdout buffering. Since then much has changed\nand this appears to no longer be needed, while also being actively\nharmful. Disabling of stdout buffering is not needed because printing\nis done (in LinePrinter::Print) either with WriteConsoleOutput (which\nis unaffected by stdout buffering) or by printf followed by fflush.\n\nMeanwhile, the unbuffered printing in the printf case causes dramatic\nslowdowns which are most visible in dry-run builds, as documented in\nissue #2084.\n\nThis fixes issue #2084, finishing off the incomplete buffering fix done\nin pull request #2031.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "df39ba92d1f8fef6d74059ae37dd67d3adcda68a",
      "old_mode": 33188,
      "old_path": "src/ninja.cc",
      "new_id": "71dea210df07263fad072d8e7683949866ce83d9",
      "new_mode": 33188,
      "new_path": "src/ninja.cc"
    }
  ]
}