)]}'
{
  "log": [
    {
      "commit": "60e78d2c993e58d890596d951fff77d5965adcd6",
      "tree": "3d53ed7254c613ef8d8de36fdceda25bc493f4f7",
      "parents": [
        "637d020a02cd734bf27acfc56c6d942cddd9eb80"
      ],
      "author": {
        "name": "Abhishek Kulkarni",
        "email": "adkulkar@umail.iu.edu",
        "time": "Wed Sep 23 13:00:27 2009 -0500"
      },
      "committer": {
        "name": "Eric Van Hensbergen",
        "email": "ericvh@strongmad.austin.ibm.com",
        "time": "Wed Sep 23 13:03:46 2009 -0500"
      },
      "message": "9p: Add fscache support to 9p\n\nThis patch adds a persistent, read-only caching facility for\n9p clients using the FS-Cache caching backend.\n\nWhen the fscache facility is enabled, each inode is associated\nwith a corresponding vcookie which is an index into the FS-Cache\nindexing tree. The FS-Cache indexing tree is indexed at 3 levels:\n- session object associated with each mount.\n- inode/vcookie\n- actual data (pages)\n\nA cache tag is chosen randomly for each session. These tags can\nbe read off /sys/fs/9p/caches and can be passed as a mount-time\nparameter to re-attach to the specified caching session.\n\nSigned-off-by: Abhishek Kulkarni \u003cadkulkar@umail.iu.edu\u003e\nSigned-off-by: Eric Van Hensbergen \u003cericvh@gmail.com\u003e\n"
    }
  ]
}
