)]}'
{
  "commit": "28be5440044d5b19b0331f79fb3e81845ad6d77e",
  "tree": "859ca1c5cc4fe3787b67e26e6b19f0a6b4900278",
  "parents": [
    "92d31920b84f258badf206eea8aaf5ac677ac535"
  ],
  "author": {
    "name": "Gerrit Renker",
    "email": "gerrit@erg.abdn.ac.uk",
    "time": "Thu Dec 13 12:16:23 2007 -0200"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Mon Jan 28 14:57:47 2008 -0800"
  },
  "message": "[DCCP]: Use maximum-RTO backoff from DCCP spec\n\nThis removes another Fixme, using the TCP maximum RTO rather than the value\nspecified by the DCCP specification. Across the sections in RFC 4340, 64\nseconds is consistently suggested as maximum RTO backoff value; and this is\nthe value which is now used.\n\nI have checked both termination cases for retransmissions of Close/CloseReq:\nwith the default value 15 of `retries2\u0027, and an initial icsk_retransmit \u003d 0,\nit takes about 614 seconds to declare a non-responding peer as dead, after\nwhich the final terminating Reset is sent. With the TCP maximum RTO value of\n120 seconds it takes (as might be expected) almost twice as long, about 23\nminutes.\n\nSigned-off-by: Gerrit Renker \u003cgerrit@erg.abdn.ac.uk\u003e\nSigned-off-by: Ian McDonald \u003cian.mcdonald@jandi.co.nz\u003e\nSigned-off-by: Arnaldo Carvalho de Melo \u003cacme@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "07dcbe73b50c4323142e8a53641257f938cb464e",
      "old_mode": 33188,
      "old_path": "net/dccp/dccp.h",
      "new_id": "3af3320194f005b1cf513b80d89da27076c215b2",
      "new_mode": 33188,
      "new_path": "net/dccp/dccp.h"
    }
  ]
}