From: Filip Navara <filip.navara@gmail.com>
To: git@vger.kernel.org
Cc: tortoisegit-dev@googlegroups.com
Subject: git-mailsplit and TortoiseGit bugs
Date: Mon, 22 Jun 2009 19:53:51 +0200 [thread overview]
Message-ID: <5b31733c0906221053k4b2659bev1da861b8e997eb5f@mail.gmail.com> (raw)
Hello,
I'd like to report a bug. There's an incompatibility between the way
TortoiseGit sends patches by e-mail and their handling by
git-mailsplit. The mail sent by TortoiseGit specifies the Content-Type
header as "Content-Type: text/plain;
boundary=WC_MAIL_PaRt_BoUnDaRy_05151998". git-mailsplit then
misinterprets it and treats it as empty patch. While TortoiseGit
should not be sending the boundary parameter, it is perfectly valid
e-mail according to RFC 5322 and MIME RFCs. The "boundary" parameter
should be ignored for anything but "multipart" Content-Types.
Best regards,
Filip Navara
P.S. I'm not subscribed to the mailing lists, so please CC me if you reply.
next reply other threads:[~2009-06-22 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 17:53 Filip Navara [this message]
2009-06-22 20:29 ` git-mailsplit and TortoiseGit bugs Jeff King
2009-06-22 21:46 ` Filip Navara
2009-06-23 1:26 ` Frank Li
2009-06-23 8:13 ` Filip Navara
2009-06-23 4:41 ` Junio C Hamano
2009-06-23 4:42 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b31733c0906221053k4b2659bev1da861b8e997eb5f@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=git@vger.kernel.org \
--cc=tortoisegit-dev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).