)]}'
{
  "commit": "4159175058987cb68aefd0e9eec2598b795363b4",
  "tree": "452a3ef5f8f2ae4c79095519078383fe766d69ab",
  "parents": [
    "de9a55b841132f7ae097f6e31ccebad2d5030cf5"
  ],
  "author": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Mon Jun 15 03:41:23 2009 -0400"
  },
  "committer": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Mon Jun 15 03:41:23 2009 -0400"
  },
  "message": "ext4: Don\u0027t update ctime for non-extent-mapped inodes\n\nThe VFS handles updating ctime, so we don\u0027t need to update the inode\u0027s\nctime in ext4_splace_branch() to update the direct or indirect blocks.\nThis was harmless when we did this in ext3, but in ext4, thanks to\ndelayed allocation, updating the ctime in ext4_splice_branch() can\ncause the ctime to mysteriously jump when the blocks are finally\nallocated.\n\nThanks to Björn Steinbrink for pointing out this problem on the git\nmailing list.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d0908afbd5bfaadb8c18fbe0383659b6d50d5e1",
      "old_mode": 33188,
      "old_path": "fs/ext4/inode.c",
      "new_id": "7c17ae275af4c0a0910bf5e7af7bc243199889de",
      "new_mode": 33188,
      "new_path": "fs/ext4/inode.c"
    }
  ]
}
