)]}'
{
  "log": [
    {
      "commit": "ebc3f64b864fc16a594c2e63bf55a55c7d42084b",
      "tree": "95040f32ad5902051527b91966118e565d48865b",
      "parents": [
        "cb65d506c34c86df5bcef939ce5a8666a451bd8b"
      ],
      "author": {
        "name": "Shaun Pereira",
        "email": "spereira@tusc.com.au",
        "time": "Wed Jun 22 22:16:17 2005 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Wed Jun 22 22:16:17 2005 -0700"
      },
      "message": "[X25]: Fast select with no restriction on response\n\nThis patch is a follow up to patch 1 regarding \"Selective Sub Address\nmatching with call user data\".  It allows use of the Fast-Select-Acceptance\noptional user facility for X.25.\n\nThis patch just implements fast select with no restriction on response\n(NRR).  What this means (according to ITU-T Recomendation 10/96 section\n6.16) is that if in an incoming call packet, the relevant facility bits are\nset for fast-select-NRR, then the called DTE can issue a direct response to\nthe incoming packet using a call-accepted packet that contains\ncall-user-data.  This patch allows such a response.  \n\nThe called DTE can also respond with a clear-request packet that contains\ncall-user-data.  However, this feature is currently not implemented by the\npatch.\n\nHow is Fast Select Acceptance used?\nBy default, the system does not allow fast select acceptance (as before).\nTo enable a response to fast select acceptance,  \nAfter a listen socket in created and bound as follows\n\tsocket(AF_X25, SOCK_SEQPACKET, 0);\n\tbind(call_soc, (struct sockaddr *)\u0026locl_addr, sizeof(locl_addr));\nbut before a listen system call is made, the following ioctl should be used.\n\tioctl(call_soc,SIOCX25CALLACCPTAPPRV);\nNow the listen system call can be made\n\tlisten(call_soc, 4);\nAfter this, an incoming-call packet will be accepted, but no call-accepted \npacket will be sent back until the following system call is made on the socket\nthat accepts the call\n\tioctl(vc_soc,SIOCX25SENDCALLACCPT);\nThe network (or cisco xot router used for testing here) will allow the \napplication server\u0027s call-user-data in the call-accepted packet, \nprovided the call-request was made with Fast-select NRR.\n\nSigned-off-by: Shaun Pereira \u003cspereira@tusc.com.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "cb65d506c34c86df5bcef939ce5a8666a451bd8b",
      "tree": "4cf281ba2e90c9c20d28a80d1efc8292aaba699a",
      "parents": [
        "68d318720052154bc6b2513b0f15d0d947cc53c9"
      ],
      "author": {
        "name": "Shaun Pereira",
        "email": "spereira@tusc.com.au",
        "time": "Wed Jun 22 22:15:01 2005 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Wed Jun 22 22:15:01 2005 -0700"
      },
      "message": "[X25]: Selective sub-address matching with call user data.\n\nFrom: Shaun Pereira \u003cspereira@tusc.com.au\u003e\n\nThis is the first (independent of the second) patch of two that I am\nworking on with x25 on linux (tested with xot on a cisco router).  Details\nare as follows.\n\nCurrent state of module:\n\nA server using the current implementation (2.6.11.7) of the x25 module will\naccept a call request/ incoming call packet at the listening x.25 address,\nfrom all callers to that address, as long as NO call user data is present\nin the packet header.\n\nIf the server needs to choose to accept a particular call request/ incoming\ncall packet arriving at its listening x25 address, then the kernel has to\nallow a match of call user data present in the call request packet with its\nown.  This is required when multiple servers listen at the same x25 address\nand device interface.  The kernel currently matches ALL call user data, if\npresent.\n\nCurrent Changes:\n\nThis patch is a follow up to the patch submitted previously by Andrew\nHendry, and allows the user to selectively control the number of octets of\ncall user data in the call request packet, that the kernel will match.  By\ndefault no call user data is matched, even if call user data is present. \nTo allow call user data matching, a cudmatchlength \u003e 0 has to be passed\ninto the kernel after which the passed number of octets will be matched. \nOtherwise the kernel behavior is exactly as the original implementation.\n\nThis patch also ensures that as is normally the case, no call user data\nwill be present in the Call accepted / call connected packet sent back to\nthe caller \n\nFuture Changes on next patch:\n\nThere are cases however when call user data may be present in the call\naccepted packet.  According to the X.25 recommendation (ITU-T 10/96)\nsection 5.2.3.2 call user data may be present in the call accepted packet\nprovided the fast select facility is used.  My next patch will include this\nfast select utility and the ability to send up to 128 octets call user data\nin the call accepted packet provided the fast select facility is used.  I\nam currently testing this, again with xot on linux and cisco.  \n\nSigned-off-by: Shaun Pereira \u003cspereira@tusc.com.au\u003e\n\n(With a fix from Alexey Dobriyan \u003cadobriyan@gmail.com\u003e)\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\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"
    }
  ]
}