)]}'
{
  "log": [
    {
      "commit": "6d41807614151829ae17a3a58bff8572af5e407e",
      "tree": "8d507b9ed679e2a42f9e1c8f4e7ba5a958360ea2",
      "parents": [
        "f4b9a988685da6386d7f9a72df3098bcc3270526"
      ],
      "author": {
        "name": "Theodore Ts\u0027o",
        "email": "tytso@mit.edu",
        "time": "Mon Aug 10 16:03:43 2009 -0400"
      },
      "committer": {
        "name": "Jan Kara",
        "email": "jack@suse.cz",
        "time": "Mon Aug 24 16:48:32 2009 +0200"
      },
      "message": "ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED\n\nThe old description for this configuration option was perhaps not\ncompletely balanced in terms of describing the tradeoffs of using a\ndefault of data\u003dwriteback vs. data\u003dordered.  Despite the fact that old\ndescription very strongly recomended disabling this feature, all of\nthe major distributions have elected to preserve the existing \u0027legacy\u0027\ndefault, which is a strong hint that it perhaps wasn\u0027t telling the\nwhole story.\n\nThis revised description has been vetted by a number of ext3\ndevelopers as being better at informing the user about the tradeoffs\nof enabling or disabling this configuration feature.\n\nCc: linux-ext4@vger.kernel.org\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\n"
    },
    {
      "commit": "bbae8bcc49bc4d002221dab52c79a50a82e7cd1f",
      "tree": "7144a78d9f734734e977cef45c012a1cd4e98008",
      "parents": [
        "e0724bf6e4a1f2e678d2b2aab01cae22e17862f0"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon Apr 06 17:16:47 2009 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon Apr 06 17:16:47 2009 -0700"
      },
      "message": "ext3: make default data ordering mode configurable\n\nThis makes the defautl ext3 data ordering mode (when no explicit\nordering is set) configurable, so as to allow people to default to\n\u0027data\u003dwriteback\u0027 and get the resulting latency improvements.\n\nThis is a non-issue if a filesystem has been explicitly set to some\nordering (with \u0027tune2fs\u0027).\n\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    },
    {
      "commit": "6da0b38f4433fb0f24615449d7966471b6e5eae0",
      "tree": "9f163fbbc7342406bb602de447293c0b11628c6f",
      "parents": [
        "0d468300dc97d6aec084799ffe39253ac366f1e4"
      ],
      "author": {
        "name": "Alexey Dobriyan",
        "email": "adobriyan@gmail.com",
        "time": "Mon Oct 20 22:28:45 2008 +0400"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon Oct 20 11:43:59 2008 -0700"
      },
      "message": "fs/Kconfig: move ext2, ext3, ext4, JBD, JBD2 out\n\nUse fs/*/Kconfig more, which is good because everything related to one\nfilesystem is in one place and fs/Kconfig is quite fat.\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    }
  ]
}