Re: [PATCH] Port git-tag.sh to C.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Port git-tag.sh to C.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:15

Jeff King [off-list ref] writes:
This is the same git-send-email bug that we fixed recently (missing
MIME-Version header). Just look for the vger "we munged your message"
headers in the version you received.
Ahh.  You are right.  The message does have these:

        X-Warning: Original message contained 8-bit characters, however during
                   the SMTP transport session the receiving system did not announce
                   capability of receiving 8-bit SMTP (RFC 1651-1653), and as this
                   message does not have MIME headers (RFC 2045-2049) to enable
                   encoding change, we had very little choice.
        X-Warning: We ASSUME it is less harmful to add the MIME headers, and
                   convert the text to Quoted-Printable, than not to do so,
                   and to strip the message to 7-bits.. (RFC 1428 Appendix A)
        X-Warning: We don't know what character set the user used, thus we had to
                   write these MIME-headers with our local system default value.

Re: [PATCH] Port git-tag.sh to C.

From: Jeff King <hidden>
Date: 2016-06-15 22:43:15

On Sun, Jun 10, 2007 at 03:19:00PM -0700, Junio C Hamano wrote:
quoted
This is the same git-send-email bug that we fixed recently (missing
MIME-Version header). Just look for the vger "we munged your message"
headers in the version you received.
Ahh.  You are right.  The message does have these:
Yes, it's easy for me to tell because I get his messages intact. :) Not
to mention his X-Mailer mentions git-send-email 1.5.0.6.

Kristian, the fix is in git 1.5.1.5 and later, if it's not too much
trouble to upgrade.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help