)]}'
{
  "commit": "8ba8e95ed14a2771bbcb43300feda094f298853e",
  "tree": "8f487c4f31175eea531fbf7305c91819eca17bec",
  "parents": [
    "36a891b67f95fd5e1442fc0f7f953809b94b3fbc"
  ],
  "author": {
    "name": "Kalin KOZHUHAROV",
    "email": "kalin@thinrope.net",
    "time": "Sat Apr 01 01:41:22 2006 +0200"
  },
  "committer": {
    "name": "Adrian Bunk",
    "email": "bunk@stusta.de",
    "time": "Sat Apr 01 01:41:22 2006 +0200"
  },
  "message": "Fix comments: s/granuality/granularity/\n\nI was grepping through the code and some `grep ganularity -R .` didn\u0027t\ncatch what I thought. Then looking closer I saw the term \"granuality\"\nused in only four places (in comments) and granularity in many more\nplaces describing the same idea. Some other facts:\n\ndictionary.com does not know such a word\ndefine:granuality on google is not found (and pages for granuality are\nmostly related to patches to the kernel)\nit has not been discussed as a term on LKML, AFAICS (\u003dCan Search)\n\nTo be consistent, I think granularity should be used everywhere.\n\nSigned-off-by: Kalin KOZHUHAROV \u003ckalin@thinrope.net\u003e\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ed7e602d70334cf1a2a8a8ec005fa48f800afb2",
      "old_mode": 33188,
      "old_path": "include/linux/fs.h",
      "new_id": "1e9ebaba07b7a2d1c8436ef95cdb5b5799dc1fce",
      "new_mode": 33188,
      "new_path": "include/linux/fs.h"
    },
    {
      "type": "modify",
      "old_id": "ff8e7019c4c498ffbc191fa16cab56f648af74b3",
      "old_mode": 33188,
      "old_path": "kernel/time.c",
      "new_id": "b00ddc71cedb860f5793978a13868e4de5862f0f",
      "new_mode": 33188,
      "new_path": "kernel/time.c"
    }
  ]
}