)]}'
{
  "commit": "73ed8c7916780b44205970848757956cd2b8c53d",
  "tree": "b381064717da353bd51135d1f95b9a4e2032fa7c",
  "parents": [
    "8967ff44d94d9bc944878811d91b638bfb3eee60"
  ],
  "author": {
    "name": "James Bottomley",
    "email": "James.Bottomley@HansenPartnership.com",
    "time": "Tue Oct 09 08:11:10 2018 -0700"
  },
  "committer": {
    "name": "James Bottomley",
    "email": "James.Bottomley@HansenPartnership.com",
    "time": "Wed Oct 17 12:19:07 2018 -0700"
  },
  "message": "code-of-conduct: Add back the TAB as the central reporting point\n\nAdd a Reporting section where the Enforcement section used to be.  The\nintention is still to debate what should go here, but in the meantime, this\ngives us back the central reporting point we had in the old code of conflict.\n\nReviewed-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nReviewed-by: Mauro Carvalho Chehab \u003cmchehab@kernel.org\u003e\nAcked-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nAcked-by: Shuah Khan \u003cshuah@kernel.org\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\n\n---\n\nv2: Added this patch to allay concerns we were stripping the reporting\n    mechanism entirely.\nv3: Add (where required by law) as a qualifier to the confidentiality\n    requirement\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4dd90987305bfbf66e2239e09e8b97a5de836e0d",
      "old_mode": 33188,
      "old_path": "Documentation/process/code-of-conduct.rst",
      "new_id": "eec768471a4d5b046a3b83b36f0ba65e35b4da91",
      "new_mode": 33188,
      "new_path": "Documentation/process/code-of-conduct.rst"
    }
  ]
}