On Tue, Mar 25, 2008 at 2:31 PM, Teemu Likonen <tlikonen@xxxxxx> wrote: > Junio C Hamano kirjoitti: > > > Samuel Tardieu <sam@xxxxxxxxxxx> writes: > > > Add MIME-Version/Content-Type/Content-Transfer-Encoding headers in > > > messages generated with git-format-patch. Without it, messages > > > generated without using --attach or --inline didn't have any > > > content type information. > > > > Isn't that job for send-email (or user's MUA)? I really do not think > > we want to clutter format-patch output any more than necessary. > > By the way, 'git send-email --compose' does not add MIME headers to > introductory message. All non-Ascii chars will output something > undefined in receivers' end. > > I guess the right way would be to detect user's charset (locale) and add > appropriate MIME headers. Also, the Subject field should be encoded if > it contains non-Ascii characters. I stuck this in my config and it works-for-me: [format] headers = \ "MIME-Version: 1.0\n\ Content-Type: text/plain; charset=UTF-8\n\ Content-Transfer-Encoding: 8bit\n" Shrug. (Never tried putting non-ascii in the subject tho.) j. -- 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
