)]}'
{
  "commit": "100bd4bb3ede667e570618a6f6929c14e7e56e4f",
  "tree": "b8b7d9400a38c4224c479538c3e240b8a35d6e0a",
  "parents": [
    "087161f5c849e2de1fddccaf55cbb7ad709b918c"
  ],
  "author": {
    "name": "Sasa Zivkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Mon Nov 07 14:58:46 2011 +0100"
  },
  "committer": {
    "name": "Sasa Zivkov",
    "email": "sasa.zivkov@sap.com",
    "time": "Wed Nov 09 08:37:19 2011 +0100"
  },
  "message": "Read timeout parameter for LDAP connections: ldap.readTimeout\n\nBy default LDAP connection would wait indefinitely on an LDAP\nrequest to return. In case LDAP server is very slow this may cause\nall SSH command creation threads to get blocked.\n\nThis change introduces the ldap.readTimeout parameter. The value\nis in the usual time-unit format i.e. \"1 s\", \"100 ms\", etc...\n\nA timed-out LDAP request seems not to cause failure of the SSH command\nfor which the LDAP request was fired. Instead, the exception is\nhandled in the PopulatingCache.get method where it is logged and the\ncreator.missing(key) is returned. This seems to be expected behaviour.\n\nChange-Id: I278b324018934a77a2886878b89c4f0c0f4ae65e\nSigned-off-by: Sasa Zivkov \u003csasa.zivkov@sap.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b817348983a9bba7522b5e39b7538574a00463c",
      "old_mode": 33188,
      "old_path": "Documentation/config-gerrit.txt",
      "new_id": "7c0b836ee697e117ffa0e3de851c98233b82e583",
      "new_mode": 33188,
      "new_path": "Documentation/config-gerrit.txt"
    },
    {
      "type": "modify",
      "old_id": "e11e9bb78b4b50f996db7c654c0afc5b69ca1cb3",
      "old_mode": 33188,
      "old_path": "gerrit-server/src/main/java/com/google/gerrit/server/auth/ldap/Helper.java",
      "new_id": "4dd47428e7662c20ddf82e40fceec0574d441263",
      "new_mode": 33188,
      "new_path": "gerrit-server/src/main/java/com/google/gerrit/server/auth/ldap/Helper.java"
    }
  ]
}