)]}'
{
  "log": [
    {
      "commit": "304c209c9b02b0386024d037fa49b273caa0575b",
      "tree": "a3d3d5903abe7cee4c465e1377c26cf4a1ca02d1",
      "parents": [
        "2c12a74cc4aeaebc378aa40ee11c7761a8ed05e0"
      ],
      "author": {
        "name": "David S. Miller",
        "email": "davem@sunset.davemloft.net",
        "time": "Mon Feb 26 15:45:15 2007 -0800"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@sunset.davemloft.net",
        "time": "Wed Feb 28 09:41:59 2007 -0800"
      },
      "message": "[NET]: Revert socket.h/stat.h ifdef hacks.\n\nThis reverts 57a87bb0720a5cf7a9ece49a8c8ed288398fd1bb.\n\nAs H. Peter Anvin states, this change broke klibc and it\u0027s\nnot very easy to fix things up without duplicating everything\ninto userspace.\n\nIn the longer term we should have a better solution to this\nproblem, but for now let\u0027s unbreak things.\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "57a87bb0720a5cf7a9ece49a8c8ed288398fd1bb",
      "tree": "eb90add73a66e6452ad6990f422803e0679dbd9a",
      "parents": [
        "4564f9e5fd00767d11fcf61e0d52787706dfcc87"
      ],
      "author": {
        "name": "Mike Frysinger",
        "email": "vapier.adi@gmail.com",
        "time": "Sat Feb 10 01:45:01 2007 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@woody.linux-foundation.org",
        "time": "Sun Feb 11 10:51:26 2007 -0800"
      },
      "message": "[PATCH] scrub non-__GLIBC__ checks in linux/socket.h and linux/stat.h\n\nUserspace should be worrying about userspace, so having the socket.h\nand stat.h pollute the namespace in the non-glibc case is wrong and\npretty much prevents any other libc from utilizing these headers\nsanely unless they set up the __GLIBC__ define themselves (which\nsucks)\n\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": "afefdbb28a0a2af689926c30b94a14aea6036719",
      "tree": "6ee500575cac928cd90045bcf5b691cf2b8daa09",
      "parents": [
        "1d32849b14bc8792e6f35ab27dd990d74b16126c"
      ],
      "author": {
        "name": "David Howells",
        "email": "dhowells@redhat.com",
        "time": "Tue Oct 03 01:13:46 2006 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Tue Oct 03 08:03:40 2006 -0700"
      },
      "message": "[PATCH] VFS: Make filldir_t and struct kstat deal in 64-bit inode numbers\n\nThese patches make the kernel pass 64-bit inode numbers internally when\ncommunicating to userspace, even on a 32-bit system.  They are required\nbecause some filesystems have intrinsic 64-bit inode numbers: NFS3+ and XFS\nfor example.  The 64-bit inode numbers are then propagated to userspace\nautomatically where the arch supports it.\n\nProblems have been seen with userspace (eg: ld.so) using the 64-bit inode\nnumber returned by stat64() or getdents64() to differentiate files, and\nfailing because the 64-bit inode number space was compressed to 32-bits, and\nso overlaps occur.\n\nThis patch:\n\nMake filldir_t take a 64-bit inode number and struct kstat carry a 64-bit\ninode number so that 64-bit inode numbers can be passed back to userspace.\n\nThe stat functions then returns the full 64-bit inode number where\navailable and where possible.  If it is not possible to represent the inode\nnumber supplied by the filesystem in the field provided by userspace, then\nerror EOVERFLOW will be issued.\n\nSimilarly, the getdents/readdir functions now pass the full 64-bit inode\nnumber to userspace where possible, returning EOVERFLOW instead when a\ndirectory entry is encountered that can\u0027t be properly represented.\n\nNote that this means that some inodes will not be stat\u0027able on a 32-bit\nsystem with old libraries where they were before - but it does mean that\nthere will be no ambiguity over what a 32-bit inode number refers to.\n\nNote similarly that directory scans may be cut short with an error on a\n32-bit system with old libraries where the scan would work before for the\nsame reasons.\n\nIt is judged unlikely that this situation will occur because modern glibc\nuses 64-bit capable versions of stat and getdents class functions\nexclusively, and that older systems are unlikely to encounter\nunrepresentable inode numbers anyway.\n\n[akpm: alpha build fix]\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nCc: Trond Myklebust \u003ctrond.myklebust@fys.uio.no\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "abcb6c9fd13fc2ad7757b818924dc8109a0e3775",
      "tree": "39a1d5660d2bd92cffa8eef09d489b241e4072a1",
      "parents": [
        "93d2341c750cda0df48a6cc67b35fe25f1ec47df"
      ],
      "author": {
        "name": "Takashi Sato",
        "email": "sho@tnes.nec.co.jp",
        "time": "Sun Mar 26 01:37:51 2006 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Sun Mar 26 08:57:00 2006 -0800"
      },
      "message": "[PATCH] 2TB files: st_blocks is invalid when calling stat64\n\nThis patch series fixes the following problems on 32 bits architecture.\n\no stat64 returns the lower 32 bits of blocks, although userland st_blocks\n  has 64 bits, because i_blocks has only 32 bits.  The ioctl with FIOQSIZE has\n  the same problem.\n\no As Dave Kleikamp said, making \u003e2TB file on JFS results in writing an\n  invalid block number to disk inode.  The cause is the same as above too.\n\no In generic quota code dquot_transfer(), the file usage is calculated from\n  i_blocks via inode_get_bytes().  If the file is over 2TB, the change of\n  usage is less than expected.  The cause is the same as above too.\n\no As Trond Myklebust said, statfs64\u0027s entries related to blocks are invalid\n  on statfs64 for a network filesystem which has more than 2^32-1 blocks with\n  CONFIG_LBD disabled.  [PATCH 3/3]\n\nWe made patches to fix problems that occur when handling a large filesystem\nand a large file.  It was discussed on the mails titled \"stat64 for over 2TB\nfile returned invalid st_blocks\".\n\nSigned-off-by: Takashi Sato \u003csho@tnes.nec.co.jp\u003e\nCc: Dave Kleikamp \u003cshaggy@austin.ibm.com\u003e\nCc: Jan Kara \u003cjack@ucw.cz\u003e\nCc: Trond Myklebust \u003ctrond.myklebust@fys.uio.no\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\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"
    }
  ]
}