)]}'
{
  "commit": "d3a44f637ecb0a4033e521a4166710aa2f080796",
  "tree": "ee436711b41228565ef2dc046f8d094dfc4b22ba",
  "parents": [
    "59c0ea183ad1c5c2b3790caa5046e4ecfa839247"
  ],
  "author": {
    "name": "Stefan Beller",
    "email": "sbeller@google.com",
    "time": "Fri Sep 22 15:52:50 2017 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Sun Sep 24 10:41:47 2017 +0900"
  },
  "message": "Documentation/config: clarify the meaning of submodule.\u003cname\u003e.update\n\nWith more commands (that potentially change a submodule) paying attention\nto submodules as well as the recent discussion[1] on\nsubmodule.\u003cname\u003e.update, let\u0027s spell out that submodule.\u003cname\u003e.update\nis strictly to be used for configuring the \"submodule update\" command\nand not to be obeyed by other commands.\n\nThese other commands usually have a strict meaning of what they should\ndo (i.e. checkout, reset, rebase, merge) as well as have their name\noverlapping with the modes possible for submodule.\u003cname\u003e.update.\n\n[1] https://public-inbox.org/git/4283F0B0-BC1C-4ED1-8126-7E512D84484B@gmail.com/\n    submodule.\u003cname\u003e.update was set to \"none\", triggering unexpected\n    behavior as the submodule was thought to never be touched.\n    However a newer version of Git taught \u0027git pull --rebase\u0027 to also\n    populate and rebase submodules if they were active.\n    The newer options such as submodule.active and command specific\n    flags would not have triggered unexpected behavior.\n\nReported-by: Lars Schneider \u003clarsxschneider@gmail.com\u003e\nSigned-off-by: Stefan Beller \u003csbeller@google.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dc4e3f58a2d2e8a5a6753bd290d65fec4f7f7b21",
      "old_mode": 33188,
      "old_path": "Documentation/config.txt",
      "new_id": "1ac0ae6adb0460a3460084aef2302434e24ee6de",
      "new_mode": 33188,
      "new_path": "Documentation/config.txt"
    }
  ]
}