git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-mailsplit and TortoiseGit bugs

From
FNFilip Navara <filip.navara@gmail.com>
Date
Jun 22, 2009, 17:53 UTC
Message-ID
<5b31733c0906221053k4b2659bev1da861b8e997eb5f@mail.gmail.com>
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: Jeff King
Message 1 of 7 in “git-mailsplit and TortoiseGit bugs”
  1. Filip NavaraJun 22, 2009
  2. Jeff KingJun 22, 2009
  3. Filip NavaraJun 22, 2009
  4. Frank LiJun 23, 2009
  5. Filip NavaraJun 23, 2009
  6. Junio C HamanoJun 23, 2009
  7. Jeff KingJun 23, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.