Johannes Schindelin venit, vidit, dixit 09.02.2009 14:36: > Hi, > > On Mon, 9 Feb 2009, Ben Bucksch wrote: > >> On 09.02.2009 13:34, Michael J Gruber wrote: >>> Johannes Schindelin venit, vidit, dixit 08.02.2009 18:28: >>> >>>> On Sun, 8 Feb 2009, Jeremy White wrote >>>>> Essentially, the problem is well understood - Thunderbird uses >>>>> format=flowed by default, which is what mangles the patches. >>>>> >>>> I guess I'll start discouraging use of Thunderbird from now on. >> Or you could just publish: >> 1. Prefs | Advanced | General | Config Editor... >> 2. "mailnews.send_plaintext_flowed" = false > > Ah. Mhm... > >> As inline attachments, they'll show up inline in the msg viewer as well > > ... which is a moot point, as the responder has to do extra work to quote > the stuff. Definitely not my type of friendliness. > >>> I found git-send-email the more reliable and practical solution for >>> sending out patches. Put yourself in bcc and you'll have a copy in >>> TB's inbox or another folder (use filters). >> Yup, I think that's the best way - git is using email only as protocol, so >> it's good to have special clients to that, as it's a really special use. > > Aha. And putting extra comments in (manually) does not count. 'cause I > do not see send-email allowing that. There is this useful thingy called "vim" which lets you edit the 00* files... Come on, Dscho ;) >>> <sarcasm style="reality: exaggerated;"> >>> Isn't that some Linux guy? How would he matter for Mozilla? Does he even >>> know how to send HTML mail... >>> </sarcasm> >>> >> I don't think it's a matter of clue, it's a matter of background and >> attitude. > > Yeah, I think my background dictates that I stay by my word and recommend > other mailers than Thunderbird. > > It is one thing to be nice to the "average" user, but another one to be > unfriendly to the people making the internet revolution possible. I think Ben made it clear why "format flowed" is the default, and there are numerous posts in the TB/moz community which make it clear why they spell it "format flawed". The default will not change. I thought about writing an extension which let's you change the config on a per message basis. (You can already do it per folder using mnenhy, I suppose.) But then I still have to navigate from TB to my repo and include the output of git-format-patch, or dump it to an mbox (or upload to an imap drafts folder). So, even with f-f issues out of the way I would find git-send-email (+vim) to be the right tool for the job. Which is why I use it, for sending patches by e-mail, not for corresponding by e-mail. So, let's be peaceful, and talk about Mozilla's choice of hg instead ;) [No, please don't!] Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
