)]}'
{
  "log": [
    {
      "commit": "1d66c64c3cee10a465cd3f8bd9191bbeb718f650",
      "tree": "1ef3e58b8ff25f850c5bf9bbdce08001751662c5",
      "parents": [
        "86b5ac878d4a63c772d03c5017b72cc799a8f2f2"
      ],
      "author": {
        "name": "Jean Delvare",
        "email": "khali@linux-fr.org",
        "time": "Mon Apr 18 21:16:59 2005 -0700"
      },
      "committer": {
        "name": "Greg KH",
        "email": "greg@press.kroah.org",
        "time": "Mon Apr 18 21:16:59 2005 -0700"
      },
      "message": "[PATCH] I2C: Fix incorrect sysfs file permissions in it87 and via686a drivers\n\nThe it87 and via686a hardware monitoring drivers each create a sysfs\nfile named \"alarms\" in R/W mode, while they should really create it in\nread-only mode. Since we don\u0027t provide a store function for these files,\nwrite attempts to these files will do something undefined (I guess) and\nbad (I am sure). My own try resulted in a locked terminal (where I\nattempted the write) and a 100% CPU load until next reboot.\n\nAs a side note, wouldn\u0027t it make sense to check, when creating sysfs\nfiles, that readable files have a non-NULL show method, and writable\nfiles have a non-NULL store method? I know drivers are not supposed to\ndo stupid things, but there is already a BUG_ON for several conditions\nin sysfs_create_file, so maybe we could add two more?\n\nSigned-off-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    },
    {
      "commit": "86b5ac878d4a63c772d03c5017b72cc799a8f2f2",
      "tree": "ef4138c02aa447610146df63749e07c1859c3509",
      "parents": [
        "05985715756b8667cb35a3e05e1668bb8afe3298"
      ],
      "author": {
        "name": "Jean Delvare",
        "email": "khali@linux-fr.org",
        "time": "Mon Apr 18 21:16:58 2005 -0700"
      },
      "committer": {
        "name": "Greg KH",
        "email": "greg@press.kroah.org",
        "time": "Mon Apr 18 21:16:58 2005 -0700"
      },
      "message": "[PATCH] I2C: via686a cleanups\n\nHere comes a small cleanup patch for the via686a driver. I noticed the\nfollowing two non-fatal problems:\n\n1* The device parent is explicitely set, but it\u0027s not needed because the\ni2c core will do as the client is registered.\n\n2* snprintf is used where strlcpy would suffice.\n\nFixing them brings the via686a driver in line with what other similar\ndrivers do.\n\nSigned-off-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\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"
    }
  ]
}