)]}'
{
  "commit": "e0d48279d5a96bc02edac72c1d28fc38aed37c15",
  "tree": "27e50179fe09fefe3ffafba60e0df123c7adc555",
  "parents": [
    "810cae53e0f622d6804f063c04a83dbc3a11b7ca"
  ],
  "author": {
    "name": "Jonathan Nieder",
    "email": "jrnieder@gmail.com",
    "time": "Thu Apr 14 21:22:02 2011 -0500"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Apr 15 13:24:53 2011 -0700"
  },
  "message": "Documentation: describe the format of messages with inline patches\n\nAdd a DISCUSSION section to the \"git format-patch\" manual to encourage\npeople to send patches in a form that can be applied by \"git am\"\nautomatically.  There are two such forms:\n\n 1. The default form in which most metadata goes in the mail header\n    and the message body starts with the patch description;\n\n 2. The snipsnip form in which a message starts with pertinent\n    discussion and ends with a patch after a \"scissors\" mark.\n\nThe example requires QP encoding in the \"Subject:\" header intended for\nthe mailer to give the reader a chance to reflect on that, rather than\nbeing startled by it later.  By contrast, in-body \"From:\" and\n\"Subject:\" lines should be human-readable and not QP encoded.\n\nInspired-by: Jim Meyering \u003cjim@meyering.net\u003e\nSigned-off-by: Jonathan Nieder \u003cjrnieder@gmail.com\u003e\nImproved-by: Junio C Hamano \u003cgitster@pobox.com\u003e\nImproved-by: Drew Northup \u003cdrew.northup@maine.edu\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9dcafc6d4442b6db66df642e92336537395b9919",
      "old_mode": 33188,
      "old_path": "Documentation/git-format-patch.txt",
      "new_id": "eebfa5c64a8b967ded7090ccec83a484e255c752",
      "new_mode": 33188,
      "new_path": "Documentation/git-format-patch.txt"
    }
  ]
}