)]}'
{
  "log": [
    {
      "commit": "e4f0648fb400a05adb7c640ce8766a7011d472d3",
      "tree": "d7bee71f23f8cd630cfe6e689a10f02e6bdec190",
      "parents": [
        "61ecfa8777d0bc8e33dc0e5c2cca9b3247da2d37"
      ],
      "author": {
        "name": "Thomas Gleixner",
        "email": "tglx@linutronix.de",
        "time": "Mon Nov 07 11:15:37 2005 +0000"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Mon Nov 07 14:43:11 2005 +0100"
      },
      "message": "[MTD] user-abi: Clean up trailing white spaces\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "638d983840bb64e02c29bdd6160bb9963f4090f7",
      "tree": "f07e85847009236731f8cb2b9afcba35d40849b1",
      "parents": [
        "4843653cab0db036399f77d9355db31ce39cb8b9"
      ],
      "author": {
        "name": "Nicolas Pitre",
        "email": "nico@cam.org",
        "time": "Sat Aug 06 05:40:46 2005 +0100"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Sun Nov 06 20:12:17 2005 +0100"
      },
      "message": "{MTD] add support for Intel\u0027s \"Sibley\" flash\n\nThis updates the Primary Vendor-Specific Extended Query parsing to\nversion 1.4 in order to get the information about the Configurable\nProgramming Mode regions implemented in the Sibley flash, as well as\nselecting the appropriate write command code.\n\nThis flash does not behave like traditional NOR flash when writing data.\nWhile mtdblock should just work, further changes are needed for JFFS2 use.\n\nSigned-off-by: Nicolas Pitre \u003cnico@cam.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "90e260c84f563a4ac6b47886e8188af06f4a4a46",
      "tree": "a487cfe4fb96fc09d0102689cd1f78ba9dee3e67",
      "parents": [
        "a69dde91e8940b49bdc9920dd65ec02c6a51f85c"
      ],
      "author": {
        "name": "Thomas Gleixner",
        "email": "tglx@linutronix.de",
        "time": "Thu May 19 17:10:26 2005 +0100"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Mon May 23 13:20:45 2005 +0200"
      },
      "message": "[MTD] NAND: Honour autoplacement schemes supplied by the caller\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "8f15fd55f9bf266139b10850947e19c4e3f4e9b7",
      "tree": "3df936efbffbbd6c20dd75f51780ac37458285ff",
      "parents": [
        "3be36675d41a30ed3b192f92684f1417aa0f8bfe"
      ],
      "author": {
        "name": "Andrew Victor",
        "email": "andrew@sanpeople.com",
        "time": "Wed Feb 09 09:17:45 2005 +0000"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Mon May 23 12:28:03 2005 +0200"
      },
      "message": "[JFFS2] Add support for JFFS2-on-Dataflash devices.\n\nFor Dataflash, can_mark_obsolete \u003d false and the NAND write buffering\ncode (wbuf.c) is used.\n\nSince the DataFlash chip will automatically erase pages when writing,\nthe cleanmarkers are not needed - so cleanmarker_oob \u003d false and\ncleanmarker_size \u003d 0\n\nDataFlash page-sizes are not a power of two (they\u0027re multiples of 528\nbytes).  The SECTOR_ADDR macro (added in the previous core patch) is\nreplaced with a (slower) div/mod version if CONFIG_JFFS2_FS_DATAFLASH is\nselected.\n\nSigned-off-by: Andrew Victor \u003candrew@sanpeople.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "31f4233baeaaeb7c563d2766781c6592ad259b6a",
      "tree": "475ffcfcc1fe91a47d6b8c413d8f25b3fdfcc1c0",
      "parents": [
        "f77814dd5728edaf1239d19755d2aa0d8c33d861"
      ],
      "author": {
        "name": "Nicolas Pitre",
        "email": "nico@cam.org",
        "time": "Tue Feb 08 17:45:55 2005 +0000"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Mon May 23 12:26:04 2005 +0200"
      },
      "message": "[MTD] User interface to Protection Registers\n\nThis is implemented using a ioctl to switch the MTD char device into\none of the different OTP \"modes\", at which point read/write/seek can\noperate on the selected OTP area.  Also some extra ioctls to query\nfor size and lock protection segments or groups.  Some example user\nspace utilities are provided.\n\nSigned-off-by: Nicolas Pitre \u003cnico@cam.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "f77814dd5728edaf1239d19755d2aa0d8c33d861",
      "tree": "5cf7f73aa367bf152e5fbd16b5173e18bb787dd5",
      "parents": [
        "67d9e95c393d23c229836e28b262dc73d71da784"
      ],
      "author": {
        "name": "Nicolas Pitre",
        "email": "nico@cam.org",
        "time": "Tue Feb 08 17:11:19 2005 +0000"
      },
      "committer": {
        "name": "Thomas Gleixner",
        "email": "tglx@mtd.linutronix.de",
        "time": "Mon May 23 12:25:23 2005 +0200"
      },
      "message": "[MTD] Support for protection register support on Intel FLASH chips\n\nThis enables support for reading, writing and locking so called\n\"Protection Registers\" present on some flash chips.\nA subset of them are pre-programmed at the factory with a\nunique set of values. The rest is user-programmable.\n\nSigned-off-by: Nicolas Pitre \u003cnico@cam.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n"
    },
    {
      "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
      "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d",
      "parents": [],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n"
    }
  ]
}