{"thread":{"id":"32087","subject":"\"git imap-send\" with HTML preformatting broken for multipart messages","startedAt":"2012-11-12T08:43:13Z","lastAt":"2012-11-12T08:43:13Z","messageCount":1,"participants":["Michael Haggerty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"202946","messageId":"50A0B6A1.80101@alum.mit.edu","threadId":"32087","inReplyTo":null,"subject":"\"git imap-send\" with HTML preformatting broken for multipart messages","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2012-11-12T08:43:13Z","receivedAt":"2012-11-12T08:43:13Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"I just noticed that \"git imap-send\" with imap.preformattedHTML turned on\nis broken for multipart messages.  The problem is that \"git imap-send\"\nembeds *everything* after the main email header in <pre></pre> and\nHTML-escapes it, instead of splitting out the email parts and quoting\ntheir bodies individually.\n\nIronically, the \"git imap-send\" manpage specifically lists the typical\nusage as\n\n    git format-patch --signoff --stdout --attach origin | git imap-send\n\nwhich is broken if imap.preformattedHTML is set.\n\nIt seems to me that rather than fix \"git imap-send\" (which would require\nit to become more complicated), it would be better to teach \"git\nformat-patch\" how to do preformatting and restrict \"git imap-send\" to\nsending messages verbatim to an IMAP server.  Moving the functionality\nto \"git format-patch\" would also make it possible to create preformatted\nemails to be used with other transports.\n\nOh, and, by the way, \"git imap-send\" is utterly untested by the test\nsuite.  The fact that it is intrinsically hard to test without lots of\nextra infrastructure is another argument for making it as stupid as\npossible.\n\nI don't plan to work on this.\n\nMichael\n\n-- \nMichael Haggerty\nmhagger@alum.mit.edu\nhttp://softwareswirl.blogspot.com/\n"}]}