)]}'
{
  "commit": "8d8140843501107c92e2f9a5acb60ee136352c1f",
  "tree": "2eda57e5aa49f7ecc457e0385538e7b2258e88cf",
  "parents": [
    "bb29456c89599acfc3ef3046e6a55ce0f48c9865"
  ],
  "author": {
    "name": "Paolo Bonzini",
    "email": "pbonzini@redhat.com",
    "time": "Tue Nov 25 15:00:27 2014 +0100"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Nov 25 14:00:15 2014 -0800"
  },
  "message": "git-send-email: add --transfer-encoding option\n\nThe thread at http://thread.gmane.org/gmane.comp.version-control.git/257392\ndetails problems when applying patches with \"git am\" in a repository with\nCRLF line endings.  In the example in the thread, the repository originated\nfrom \"git-svn\" so it is not possible to use core.eol and friends on it.\n\nRight now, the best option is to use \"git am --keep-cr\".  However, when\na patch create new files, the patch application process will reject the\nnew file because it finds a \"/dev/null\\r\" string instead of \"/dev/null\".\n\nThe problem is that SMTP transport is CRLF-unsafe.  Sending a patch by\nemail is the same as passing it through \"dos2unix | unix2dos\".  The newly\nintroduced CRLFs are normally transparent because git-am strips them. The\nkeepcr\u003dtrue setting preserves them, but it is mostly working by chance\nand it would be very problematic to have a \"git am\" workflow in a\nrepository with mixed LF and CRLF line endings.\n\nThe MIME solution to this is the quoted-printable transfer enconding.\nThis is not something that we want to enable by default, since it makes\nreceived emails horrible to look at.  However, it is a very good match\nfor projects that store CRLF line endings in the repository.\n\nThe only disadvantage of quoted-printable is that quoted-printable\npatches fail to apply if the maintainer uses \"git am --keep-cr\".  This\nis because the decoded patch will have two carriage returns at the end\nof the line.  Therefore, add support for base64 transfer encoding too,\nwhich makes received emails downright impossible to look at outside\na MUA, but really just works.\n\nThe patch covers all bases, including users that still live in the late\n80s, by also providing a 7bit content transfer encoding that refuses\nto send emails with non-ASCII character in them.  And finally, \"8bit\"\nwill add a Content-Transfer-Encoding header but otherwise do nothing.\n\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "922072596fdd80eaaa47746fba5e5591223c5108",
      "old_mode": 33188,
      "old_path": "Documentation/config.txt",
      "new_id": "cc2ff201be1d53cda4d35afe15b8a140b145bd6e",
      "new_mode": 33188,
      "new_path": "Documentation/config.txt"
    },
    {
      "type": "modify",
      "old_id": "a60776eb579e10507814c643cc292dfa99750aa9",
      "old_mode": 33188,
      "old_path": "Documentation/git-send-email.txt",
      "new_id": "a9efa5c2ec18776e12c5bdbb250df5b8e0f41581",
      "new_mode": 33188,
      "new_path": "Documentation/git-send-email.txt"
    },
    {
      "type": "modify",
      "old_id": "2fece98c603e24ed5ce08156e0e44199a149ba83",
      "old_mode": 33188,
      "old_path": "contrib/completion/git-completion.bash",
      "new_id": "b154f7066bbcb51e789c269600019d296cba04f4",
      "new_mode": 33188,
      "new_path": "contrib/completion/git-completion.bash"
    },
    {
      "type": "modify",
      "old_id": "b29a3045b7d91eb6c9543559e0cb909219a826dd",
      "old_mode": 33261,
      "old_path": "git-send-email.perl",
      "new_id": "82c6feaa4640e993051bfbe57df593c0f012a9ba",
      "new_mode": 33261,
      "new_path": "git-send-email.perl"
    },
    {
      "type": "modify",
      "old_id": "19a3ced600a20d805d430533b275a8fa4269b835",
      "old_mode": 33261,
      "old_path": "t/t9001-send-email.sh",
      "new_id": "e5016f457398a0770ebfc0e98d6f60fdfa4be2fc",
      "new_mode": 33261,
      "new_path": "t/t9001-send-email.sh"
    }
  ]
}