)]}'
{
  "commit": "3d6bc9a763f56156b424e7382b4029a67a49847e",
  "tree": "a4cde8ea79d82c70e7685858cbdd3c054272231e",
  "parents": [
    "e46fe3df01435bf523d2ab4f2755556c0e4e6f78"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Apr 16 08:03:14 2015 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Apr 16 08:03:14 2015 -0700"
  },
  "message": "Revert \"merge: pass verbosity flag down to merge-recursive\"\n\nThis reverts commit 2bf15a3330a26183adc8563dbeeacc11294b8a01, whose\nintention was good, but the verbosity levels used in merge-recursive\nturns out to be rather uneven.  For example, a merge of two branches\nwith conflicting submodule updates used to report CONFLICT: output\nwith --quiet but no longer (which *is* desired), while the final\n\"Automatic merge failed; fix conflicts and then commit\" message is\nstill shown even with --quiet (which *is* inconsistent).\n\nOriginally reported by Bryan Turner; it is too early to declare what\nthe concensus is, but it seems that we would need to level the\nverbosity levels used in merge strategy backends before we can go\nforward.  In the meantime, we\u0027d revert to the old behaviour until\nthat happens.\n\ncf. $gmane/267245\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "068a83b328a2429e5ab1909652a66ffb5b234382",
      "old_mode": 33188,
      "old_path": "builtin/merge.c",
      "new_id": "3b0f8f96d4168463139d15f1cde655facc73426c",
      "new_mode": 33188,
      "new_path": "builtin/merge.c"
    }
  ]
}