)]}'
{
  "log": [
    {
      "commit": "5cae841b13f23ccdf7e38b2400b5cf57deb57ccf",
      "tree": "c3e673089f4e1b5e0e5db26b370a23c2851ebd69",
      "parents": [
        "9b52523aff51e3b245e6ec8887e3fcf190da4711"
      ],
      "author": {
        "name": "Al Viro",
        "email": "viro@www.linux.org.uk",
        "time": "Wed May 04 05:39:22 2005 +0100"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Wed May 04 07:33:13 2005 -0700"
      },
      "message": "[PATCH] ISA DMA Kconfig fixes - part 1\n\nA bunch of drivers use ISA DMA helpers or their equivalents for\nplatforms that have ISA with different DMA controller (a lot of ARM\nboxen).  Currently there is no way to put such dependency in Kconfig -\nCONFIG_ISA is not it (e.g.  it is not set on platforms that have no ISA\nslots, but have on-board devices that pretend to be ISA ones).\n\nNew symbol added - ISA_DMA_API.  Set when we have functional\nenable_dma()/set_dma_mode()/etc.  set of helpers.  Next patches in the\nseries will add missing dependencies for drivers that need them.\n\nI\u0027m very carefully staying the hell out of the recurring flamefest on\nwhat exactly CONFIG_ISA would mean in ideal world - added symbol has a\nwell-defined meaning and for now I really want to treat it as completely\nindependent from the mess around CONFIG_ISA.\n\nSigned-off-by: Al Viro \u003cviro@parcelfarce.linux.theplanet.co.uk\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\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"
    }
  ]
}
