)]}'
{
  "commit": "c9b686056eeb344f21bdf259cc000ebd4fa8af65",
  "tree": "7c6fd9d5d6cf217684ed91b06bcdecc0c4ab462a",
  "parents": [
    "9555a4aae4768d0c451906a0fb5a6d2441bd3c36"
  ],
  "author": {
    "name": "Edwin Kempin",
    "email": "edwin.kempin@sap.com",
    "time": "Wed Oct 30 09:32:43 2013 +0100"
  },
  "committer": {
    "name": "Edwin Kempin",
    "email": "edwin.kempin@sap.com",
    "time": "Thu Oct 31 07:47:22 2013 +0100"
  },
  "message": "Explain limitation of storing plugin config in existing config files\n\nIn the plugin documentation it is suggested to store plugin\nconfiguration parameters in a \u0027plugin\u0027 subsection in\n\u0027gerrit.config\u0027/\u0027project.config\u0027. This approach has the limitation\nthat the plugin configuration cannot have subsections and thus it is\nonly suitable for plugins with a simple key-value pair configuration.\nPlugins that have a more complex configuration need to store their\nconfiguration in an own configuration file.\n\nChange-Id: Iac305e1bb451496034b06dbc762c8da08c97a59e\nSigned-off-by: Edwin Kempin \u003cedwin.kempin@sap.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af087477dc637c518c706f78feb239a1cf4ecdce",
      "old_mode": 33188,
      "old_path": "Documentation/dev-plugins.txt",
      "new_id": "7a35115e1f5dfee728b97684559d7b2a97208f34",
      "new_mode": 33188,
      "new_path": "Documentation/dev-plugins.txt"
    }
  ]
}