)]}'
{
  "commit": "db29a6b49674085f136331014ba0eee249c16a2c",
  "tree": "423676abaf2067b2d359a2439e00616812ee55f7",
  "parents": [
    "586cf2681f527ce8b85b9bd57c8b9f7945fbe051"
  ],
  "author": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Tue Apr 21 09:27:03 2009 +0200"
  },
  "committer": {
    "name": "Jens Axboe",
    "email": "jens.axboe@oracle.com",
    "time": "Tue Apr 28 07:37:33 2009 +0200"
  },
  "message": "block: enable by default support for large devices and files on 32-bit archs\n\nEnable by default support for large devices and files (CONFIG_LBD):\n\n- With 1TB disks being a commodity hardware it is quite easy to hit 2TB\n  limitation while building RAIDs etc. and many distros have been using\n  CONFIG_LBD\u003dy by default already (at least Fedora 10 and openSUSE 11.1).\n\n- This should also prevent a subtle ext4 filesystem compatibility issue:\n  mke2fs.ext4 defaults to creating filesystems with huge_files feature\n  enabled and such filesystems cannot be later mounted read-write on\n  machines with CONFIG_LBD\u003dn (it should be quite easy to hit this issue\n  when trying to use filesystem created using distro kernel on system\n  running the self-build kernel, think about USB disk enclosures \u0026 co.).\n\nWhile at it:\n\n- Clarify config option help text w.r.t. mounting ext4 filesystems\n  (they can be mounted with CONFIG_LBD\u003dn but in the read-only mode).\n\nCc: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Bartlomiej Zolnierkiewicz \u003cbzolnier@gmail.com\u003e\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e7d12782bcfb5eccb56aee532b8c27fa81706499",
      "old_mode": 33188,
      "old_path": "block/Kconfig",
      "new_id": "2c39527aa7db026dc6c6b6c20fbe55024de46100",
      "new_mode": 33188,
      "new_path": "block/Kconfig"
    }
  ]
}