> 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. Gah! With all due respect, I think this attitude is a part of the problem. It is clear to me that Ben and all the Thunderbird devs are doing their level best to make the best possible MUA. Patch senders are a tiny fraction of the Thunderbird user base, and it's reasonable to down prioritize our concerns. Even so, Ben has spent a lot of time on this issue. One of my great frustrations on the bug I copied was that I thought that Robin was articulating some valid points, but then couldn't help flaming on, thereby making it much harder for any human Mozilla dev to want to help. I'd like to hope that there is a reasonable solution that works both for us and for the general public. I spent some time with the git-format-patch code as well as the Thunderbird code. I discovered that if I just injected charset=iso-2022-jp, format=flowed would stay off! <grin> Ben, along those lines, we do have the ability to control the entire body of a possible patch before Thunderbird sees it. Would it be possible, or reasonable, for Thunderbird to look for and preserve a 'format=fixed' setting inside a body that we generated? Cheers, Jeremy -- 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
