)]}'
{
  "commit": "a78ae460e4b71ab9a6c42fb84edf6640099e45eb",
  "tree": "ae841347915826a59248e434f4ee99a3ea98a9d9",
  "parents": [
    "0491ada0352a9f9d165edfd3b842271975601901"
  ],
  "author": {
    "name": "Alex Bradbury",
    "email": "asb@lowrisc.org",
    "time": "Fri Jan 03 17:24:12 2020 +0000"
  },
  "committer": {
    "name": "Alex Bradbury",
    "email": "asb@asbradbury.org",
    "time": "Mon Jan 06 18:54:32 2020 +0000"
  },
  "message": "[doc] Change back to int for loop counters in example code\n\nOur C and C++ style guide builds on top of Google\u0027s, which prefers int\nfor simple loop counters. There\u0027s relevant discussion on the advantages\nof this approach on this llvm-dev thread, which also cites a range of\nother sources:\n* http://lists.llvm.org/pipermail/llvm-dev/2019-June/132890.html\n* http://lists.llvm.org/pipermail/llvm-dev/2019-June/133023.html\n\nPR #1240 changed two loops in example code from using int to using\nsize_t as a loop counter, and this commit reverts that change.\n\nI\u0027m posting this as a PR to test the waters to see if we\u0027re happy\nsticking with our current approach or if someobody wants to champion a\nproposed change to recommend size_t for loop counters.\n\nSigned-off-by: Alex Bradbury \u003casb@lowrisc.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "791e0744c24e6579c0c2af37ed0edfdc75a11c05",
      "old_mode": 33188,
      "old_path": "hw/ip/rv_plic/doc/_index.md",
      "new_id": "1201a23b1144abd1f126577f24802d68674486e1",
      "new_mode": 33188,
      "new_path": "hw/ip/rv_plic/doc/_index.md"
    }
  ]
}