)]}'
{
  "log": [
    {
      "commit": "a02d692611348f11ee1bc37431a883c3ff2de23e",
      "tree": "5a2ad4862784b4337846b44ddd816e495484086f",
      "parents": [
        "0b10bf5e14d856d1d27a2117d07af2bebee81b75"
      ],
      "author": {
        "name": "Chuck Lever",
        "email": "chuck.lever@oracle.com",
        "time": "Sun Aug 09 15:09:34 2009 -0400"
      },
      "committer": {
        "name": "Trond Myklebust",
        "email": "Trond.Myklebust@netapp.com",
        "time": "Sun Aug 09 15:09:34 2009 -0400"
      },
      "message": "SUNRPC: Provide functions for managing universal addresses\n\nIntroduce a set of functions in the kernel\u0027s RPC implementation for\nconverting between a socket address and either a standard\npresentation address string or an RPC universal address.\n\nThe universal address functions will be used to encode and decode\nRPCB_FOO and NFSv4 SETCLIENTID arguments.  The other functions are\npart of a previous promise to deliver shared functions that can be\nused by upper-layer protocols to display and manipulate IP\naddresses.\n\nThe kernel\u0027s current address printf formatters were designed\nspecifically for kernel to user-space APIs that require a particular\nstring format for socket addresses, thus are somewhat limited for the\npurposes of sunrpc.ko.  The formatter for IPv6 addresses, %pI6, does\nnot support short-handing or scope IDs.  Also, these printf formatters\nare unique per address family, so a separate formatter string is\nrequired for printing AF_INET and AF_INET6 addresses.\n\nSigned-off-by: Chuck Lever \u003cchuck.lever@oracle.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\n"
    }
  ]
}