)]}'
{
  "log": [
    {
      "commit": "f9e86f419073605b4520848021cc042963c227c7",
      "tree": "15546406224d741234da20fc6431d6b8af76bc98",
      "parents": [
        "77293034696e3e0b6c8b8fc1f96be091104b3d2b"
      ],
      "author": {
        "name": "Roland McGrath",
        "email": "roland@redhat.com",
        "time": "Tue Jul 17 04:03:49 2007 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@woody.linux-foundation.org",
        "time": "Tue Jul 17 10:23:03 2007 -0700"
      },
      "message": "Remove CHILD_MAX\n\nThe CHILD_MAX macro in limits.h should not be there.  It claims to be the\nlimit on processes a user can own, but its value is wrong for that.\nThere is no constant value, but a variable resource limit (RLIMIT_NPROC).\nNothing in the kernel uses CHILD_MAX.\n\nThe proper thing to do according to POSIX is not to define CHILD_MAX at all.\nThe sysconf (_SC_CHILD_MAX) implementation works by calling getrlimit.\n\nSigned-off-by: Roland McGrath \u003croland@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    },
    {
      "commit": "77293034696e3e0b6c8b8fc1f96be091104b3d2b",
      "tree": "17eeff1041240f99f1a37f5b57bf59d72d0a50a1",
      "parents": [
        "c09edd6eba683741bb8aa8e388a2bfaf1c1a28f9"
      ],
      "author": {
        "name": "Roland McGrath",
        "email": "roland@redhat.com",
        "time": "Tue Jul 17 04:03:49 2007 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@woody.linux-foundation.org",
        "time": "Tue Jul 17 10:23:03 2007 -0700"
      },
      "message": "Remove OPEN_MAX\n\nThe OPEN_MAX macro in limits.h should not be there.  It claims to be the\nlimit on file descriptors in a process, but its value is wrong for that.\nThere is no constant value, but a variable resource limit (RLIMIT_NOFILE).\nNothing in the kernel uses OPEN_MAX except things that are wrong to do so.\nI\u0027ve submitted other patches to remove those uses.\n\nThe proper thing to do according to POSIX is not to define OPEN_MAX at all.\nThe sysconf (_SC_OPEN_MAX) implementation works by calling getrlimit.\n\nSigned-off-by: Roland McGrath \u003croland@redhat.com\u003e\nCc: \"David S. Miller\" \u003cdavem@davemloft.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.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"
    }
  ]
}