)]}'
{
  "commit": "af4176b49c5ee15a9c9b10720c92456b28e7aac7",
  "tree": "a8f763a172e6fc19ef6ac24f04d6b88337c8a1b6",
  "parents": [
    "12fcfd22fe5bf4fe74710232098bc101af497995"
  ],
  "author": {
    "name": "Chris Mason",
    "email": "chris.mason@oracle.com",
    "time": "Tue Mar 24 10:24:31 2009 -0400"
  },
  "committer": {
    "name": "Chris Mason",
    "email": "chris.mason@oracle.com",
    "time": "Tue Mar 24 16:14:52 2009 -0400"
  },
  "message": "Btrfs: optimize fsyncs on old files\n\nThe fsync log has code to make sure all of the parents of a file are in the\nlog along with the file.  It uses a minimal log of the parent directory\ninodes, just enough to get the parent directory on disk.\n\nIf the transaction that originally created a file is fully on disk,\nand the file hasn\u0027t been renamed or linked into other directories, we\ncan safely skip the parent directory walk.  We know the file is on disk\nsomewhere and we can go ahead and just log that single file.\n\nThis is more important now because unrelated unlinks in the parent directory\nmight make us force a commit if we try to log the parent.\n\nSigned-off-by: Chris Mason \u003cchris.mason@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1b7f04a8f168521d7c8001eb12a3ee7ed48f989c",
      "old_mode": 33188,
      "old_path": "fs/btrfs/tree-log.c",
      "new_id": "fc9b87a7975bd38f76d7e22c84cfe010e3aafa42",
      "new_mode": 33188,
      "new_path": "fs/btrfs/tree-log.c"
    }
  ]
}
