)]}'
{
  "log": [
    {
      "commit": "a6891645cf2ddd4778096848a864580e7258faba",
      "tree": "e0095e8b87e199e7310508fc3687660746860600",
      "parents": [
        "7394daa8c61dfda4baa687f133748fa0b599b017"
      ],
      "author": {
        "name": "David Howells",
        "email": "dhowells@redhat.com",
        "time": "Fri Apr 03 16:42:37 2009 +0100"
      },
      "committer": {
        "name": "David Howells",
        "email": "dhowells@redhat.com",
        "time": "Fri Apr 03 16:42:37 2009 +0100"
      },
      "message": "FS-Cache: Root index definition\n\nAdd a description of the root index of the cache for later patches to make use\nof.\n\nThe root index is owned by FS-Cache itself.  When a netfs requests caching\nfacilities, FS-Cache will, if one doesn\u0027t already exist, create an entry in\nthe root index with the key being the name of the netfs (\"AFS\" for example),\nand the auxiliary data holding the index structure version supplied by the\nnetfs:\n\n\t\t\t\t     FSDEF\n\t\t\t\t       |\n\t\t\t\t +-----------+\n\t\t\t\t |           |\n\t\t\t\tNFS         AFS\n\t\t\t       [v\u003d1]       [v\u003d1]\n\nIf an entry with the appropriate name does already exist, the version is\ncompared.  If the version is different, the entire subtree from that entry\nwill be discarded and a new entry created.\n\nThe new entry will be an index, and a cookie referring to it will be passed to\nthe netfs.  This is then the root handle by which the netfs accesses the\ncache.  It can create whatever objects it likes in that index, including\nfurther indices.\n\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nAcked-by: Steve Dickson \u003csteved@redhat.com\u003e\nAcked-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nAcked-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nTested-by: Daire Byrne \u003cDaire.Byrne@framestore.com\u003e\n"
    }
  ]
}