Re: MIME headers in introductory message (git send-email --compose)

From: Jay Soffian <jaysoffian@gmail.com>
Date: Mar 25, 2008, 20:59 UTC
Message-ID: <76718490803251359y53b505e4u781ded6df5364650@mail.gmail.com>
In-Reply-To: <7vhceuleeu.fsf@gitster.siamese.dyndns.org>

On Tue, Mar 25, 2008 at 4:47 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> "Jay Soffian" <jaysoffian@gmail.com> writes:
>
>  > 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"
>
>  I suspect that you shouldn't do this.  This would badly interfere both
>  with existing format-patch behaviour that adds these MIME-Version and
>  Content-Type headers by looking at the contents, and with recent
>  format-patch fix 6bf4f1b (format-patch: generate MIME header as needed
>  even when there is format.header, 2008-03-14) to make the detection based
>  on contents (and presense of format.headers).

Fair enough. But I never send out a patch w/o looking at it in an editor first so I would've caught that. Thanks for the heads-up though.

j.