From: Catalin Marinas <catalin.marinas@gmail.com>
To: Karl Wiberg <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [StGit PATCH] mail: Use space rather than tab for long header folding
Date: Fri, 12 Feb 2010 16:15:19 +0000 [thread overview]
Message-ID: <b0943d9e1002120815n69691e63p80146f9dcd5ff68c@mail.gmail.com> (raw)
In-Reply-To: <b8197bcb1002120809q5eb458f7pa9e9b0562af6bcda@mail.gmail.com>
On 12 February 2010 16:09, Karl Wiberg <kha@treskal.com> wrote:
> On Fri, Feb 12, 2010 at 4:39 PM, Catalin Marinas
> <catalin.marinas@arm.com> wrote:
>
>> The default Python implementation (at least 2.5 and earlier) fold long
>> e-mail header lines by inserting "\n\t". This causes issues with some
>> e-mail clients that remove both "\n\t". The RFC2822 shows that folding
>> should be done with "\n ". The Python workaround is to use a Header
>> object instead of a string when setting the message headers.
>
> Aha. If this works like I think it does, it'll eliminate the problem
> where patches with long subject lines pick up tab characters when
> imported from e-mails. But that's not the motivation you're
> describing, is it?
My main motivation is only for sending e-mails as I have an Exchange
server here which removes the tab completely sticking two words
together. If you import an e-mail sent by the patched StGit, yes, it
will solve this as well.
--
Catalin
prev parent reply other threads:[~2010-02-12 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 15:39 [StGit PATCH] mail: Use space rather than tab for long header folding Catalin Marinas
2010-02-12 16:09 ` Karl Wiberg
2010-02-12 16:15 ` Catalin Marinas [this message]
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=b0943d9e1002120815n69691e63p80146f9dcd5ff68c@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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).