)]}'
{
  "commit": "15efbe763978d7cc327d824d9e8f8f9e525dd40d",
  "tree": "b327c7e80268d2362f20f3cf8ec9dffaf33869c9",
  "parents": [
    "b90a137d30a6322d76023d879d40fc31f3edf0a6"
  ],
  "author": {
    "name": "Neil Horman",
    "email": "nhorman@tuxdriver.com",
    "time": "Fri Feb 15 09:53:59 2008 -0500"
  },
  "committer": {
    "name": "Vlad Yasevich",
    "email": "vladislav.yasevich@hp.com",
    "time": "Thu Feb 28 16:41:05 2008 -0500"
  },
  "message": "[SCTP]: Clean up naming conventions of sctp protocol/address family registration\n\nI noticed while looking into some odd behavior in sctp, that the variable\nname sctp_pf_inet6_specific was used twice to represent two different\npieces of data (its both a structure name and a pointer to that type of\nstructure), which is confusing to say the least, and potentially dangerous\ndepending on the variable scope.  This patch cleans that up, and makes the\nprotocol and address family registration names in SCTP more regular,\nincreasing readability.\n\nSigned-off-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSigned-off-by: Vlad Yasevich \u003cvladislav.yasevich@hp.com\u003e\n\n ipv6.c     |   12 ++++++------\n protocol.c |   12 ++++++------\n 2 files changed, 12 insertions(+), 12 deletions(-)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4d7ec961ae1da98c919fdb1927be5b297f94627c",
      "old_mode": 33188,
      "old_path": "net/sctp/ipv6.c",
      "new_id": "87f940587d5fe8d3cd72ff33cf0a995498e4c093",
      "new_mode": 33188,
      "new_path": "net/sctp/ipv6.c"
    },
    {
      "type": "modify",
      "old_id": "22a16571499c3bc82902941d96f2bdbdfb00eca7",
      "old_mode": 33188,
      "old_path": "net/sctp/protocol.c",
      "new_id": "688546dccd828f0821736a301535049cc3d8ca04",
      "new_mode": 33188,
      "new_path": "net/sctp/protocol.c"
    }
  ]
}