{"thread":{"id":"17681","subject":"RFC re Thunderbird + imap-send","startedAt":"2009-02-09T21:49:51Z","lastAt":"2009-02-10T19:00:57Z","messageCount":5,"participants":["Jeremy White","Michael J Gruber","Ben Bucksch"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"103907","messageId":"4990A4FF.6020404@codeweavers.com","threadId":"17681","inReplyTo":null,"subject":"RFC re Thunderbird + imap-send","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2009-02-09T21:49:51Z","receivedAt":"2009-02-09T21:49:51Z","isPatch":false,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"So, MajorDomo knows that what I'm trying is sick and twisted; I seem to\nhave run afoul of the taboos:\n  http://vger.kernel.org/majordomo-taboos.txt\n\n(ixnay on the ention may of ontentcay ypetay tmlhay :-/).\n\nSo here is a pointer to a proposed patch to enable git-imap-send to work\nwith Thunderbird, based on Ben's suggestion:\n\nhttp://www.codeweavers.com/~jwhite/0001-Add-an-option-to-wrap-a-patch-in-pre-in-git-imap-s.patch\n\nEssentially, with this patch, I add an html option to the imap-send\nserver configuration block.  If turned on, we structure each patch as\nhtml, inside of pre blocks.  And, in fact, Thunderbird does\nautomatically convert such an email into a plain/text, format=fixed\nemail, that seems to diff cleanly with a regular git-format-patch result.\n\nThoughts?  Tar and feathers?\n\nCheers,\n\nJeremy\n"},{"id":"103972","messageId":"49915FB6.8010803@drmicha.warpmail.net","threadId":"17681","inReplyTo":"4990A4FF.6020404@codeweavers.com","subject":"Re: RFC re Thunderbird + imap-send","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-02-10T11:06:30Z","receivedAt":"2009-02-10T11:06:30Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Jeremy White venit, vidit, dixit 09.02.2009 22:49:\n> So, MajorDomo knows that what I'm trying is sick and twisted; I seem to\n> have run afoul of the taboos:\n>   http://vger.kernel.org/majordomo-taboos.txt\n> \n> (ixnay on the ention may of ontentcay ypetay tmlhay :-/).\n> \n> So here is a pointer to a proposed patch to enable git-imap-send to work\n> with Thunderbird, based on Ben's suggestion:\n> \n> http://www.codeweavers.com/~jwhite/0001-Add-an-option-to-wrap-a-patch-in-pre-in-git-imap-s.patch\n> \n> Essentially, with this patch, I add an html option to the imap-send\n> server configuration block.  If turned on, we structure each patch as\n> html, inside of pre blocks.  And, in fact, Thunderbird does\n> automatically convert such an email into a plain/text, format=fixed\n> email, that seems to diff cleanly with a regular git-format-patch result.\n> \n> Thoughts?  Tar and feathers?\n\nLooks okay here. I leave the tarring and feathering to Dscho ;)\n\nTrying this out showed that indeed git-imap-send needs much more love.\nThe man page doesn't say much, doesn't describe all options. Most\noptions can be specified in config only. You can't pass file arguments,\nonly stdin. You can't even pass a recipient!\n\nTo be useful, imap-send should really obey the same config options and\nparameters as much as possible. In fact they should share some.\nimap-send and send-email should be usable interchangeably, without\nfiddling with format-patch options (which has to: and cc: where it\ndoesn't really belong). Uhm, I'm getting off-topic.\n\nBack on topic: TB does the automatic conversion to plain text only when\nthe send options are appropriate, or if you set the recipient to \"text\nonly\".\n\nAlso:\nFor a typical text mail in Drafts I see lines like\n\nX-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0\nContent-Type: text/plain; charset=ISO-8859-1; format=flowed\nContent-Transfer-Encoding: quoted-printable\n\nAny chance we could use that rather than invoke the HTML editor?\nWe would need to shut off q-p and f-f *and* avoid automatic word wrap\n(or make sure patches don't have longer lines then TBs editor allows),\nthe latter I don't know how to do.\n\nMichael\n"},{"id":"103991","messageId":"49917208.6000807@beonex.com","threadId":"17681","inReplyTo":"49915FB6.8010803@drmicha.warpmail.net","subject":"Re: RFC re Thunderbird + imap-send","fromName":"Ben Bucksch","fromEmail":"ben.bucksch.news@beonex.com","sentAt":"2009-02-10T12:24:40Z","receivedAt":"2009-02-10T12:24:40Z","isPatch":false,"sender":{"key":"ben.bucksch.news@beonex.com","avatar":null},"body":"On 10.02.2009 12:06, Michael J Gruber wrote:\n> For a typical text mail in Drafts I see lines like\n> Content-Type: text/plain; charset=ISO-8859-1; format=flowed\n> Content-Transfer-Encoding: quoted-printable\n> Any chance we could use that rather than invoke the HTML editor?\n> We would need to shut off q-p and f-f *and* avoid automatic word wrap\n> (or make sure patches don't have longer lines then TBs editor allows),\n> the latter I don't know how to do.\n>    \nI'm not aware that existing headers would influence the send logic (in \nturning on/off qp or f=f or word wrap).\n"},{"id":"104004","messageId":"49917FC4.3000807@codeweavers.com","threadId":"17681","inReplyTo":"49917208.6000807@beonex.com","subject":"Re: RFC re Thunderbird + imap-send","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2009-02-10T13:23:16Z","receivedAt":"2009-02-10T13:23:16Z","isPatch":false,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"Ben Bucksch wrote:\n> On 10.02.2009 12:06, Michael J Gruber wrote:\n>> For a typical text mail in Drafts I see lines like\n>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed\n>> Content-Transfer-Encoding: quoted-printable\n>> Any chance we could use that rather than invoke the HTML editor?\n>> We would need to shut off q-p and f-f *and* avoid automatic word wrap\n>> (or make sure patches don't have longer lines then TBs editor allows),\n>> the latter I don't know how to do.\n>>    \n> I'm not aware that existing headers would influence the send logic (in \n> turning on/off qp or f=f or word wrap).\n\nI both looked at the Thunderbird code and experimented with a variety \nof options and found no way to do this; only the charset seems to\nbe picked up (and that may actually be a bug, judging by Ben's initial\nreaction :-/).\n\nCheers,\n\nJeremy\n"},{"id":"104059","messageId":"4991CEE9.8040402@codeweavers.com","threadId":"17681","inReplyTo":"49915FB6.8010803@drmicha.warpmail.net","subject":"Re: RFC re Thunderbird + imap-send","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2009-02-10T19:00:57Z","receivedAt":"2009-02-10T19:00:57Z","isPatch":false,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"> Looks okay here. I leave the tarring and feathering to Dscho ;)\n\nThanks.\n\n> \n> Trying this out showed that indeed git-imap-send needs much more love.\n> The man page doesn't say much, doesn't describe all options. Most\n> options can be specified in config only. You can't pass file arguments,\n> only stdin. You can't even pass a recipient!\n\nHmm.  I think the documentation/man page is correct, at least in the \ntip; Rob Shearman fixed it back in July.\n\nI think your larger concerns about git-imap-send are valid; it does seem \nthat having two paths for emailing patches is less than ideal.\n\nBut I'm going to cowardly claim that is outside of my scope at this \npoint.  (I like starting flame wars and all, but adding --html to \ngit-send-email just seems like a poor choice for my health <grin>).\n\nCheers,\n\nJeremy\n"}]}