From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add a MIME-Version header to e-mails
Date: Tue, 7 Nov 2006 19:09:06 +0000 [thread overview]
Message-ID: <b0943d9e0611071109w584f4f7fv3ba1b7dbd9413717@mail.gmail.com> (raw)
In-Reply-To: <b0943d9e0611070153s2a52f65k6ed4643e60a144b3@mail.gmail.com>
On 07/11/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> I'll include these patches (maybe modified) and I'll try to fix
> "import" as well.
I re-implemented parts of the mail and import commands (inspiring from
your patches). They now use the email Python package. The mail command
encodes the body to 7 or 8bit depending on non-ascii characters. The
headers are QP-encoded. The import command can decode messages
properly and can also handle multipart e-mails.
I still have to write a test script but my simple tests showed that it
works. Please let me know if there is anything wrong (especially with
the QP-encoding of the mail headers).
Thanks.
--
next prev parent reply other threads:[~2006-11-07 19:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 9:00 [PATCH] Allow hand-editing of patches before sending Karl Hasselström
2006-11-02 10:32 ` Catalin Marinas
2006-11-02 11:36 ` Karl Hasselström
2006-11-03 9:39 ` Catalin Marinas
2006-11-03 9:58 ` Karl Hasselström
2006-11-03 10:01 ` Karl Hasselström
2006-11-03 10:21 ` Petr Baudis
2006-11-03 10:31 ` Robin Rosenberg
2006-11-03 10:36 ` Andreas Ericsson
2006-11-03 10:53 ` Karl Hasselström
2006-11-03 11:21 ` Junio C Hamano
2006-11-03 11:35 ` Karl Hasselström
2006-11-03 12:56 ` Catalin Marinas
2006-11-03 12:07 ` Andy Whitcroft
2006-11-03 12:36 ` Karl Hasselström
2006-11-03 14:03 ` Andy Whitcroft
2006-11-03 18:48 ` Linus Torvalds
2006-11-05 11:43 ` Karl Hasselström
2006-11-05 16:44 ` Linus Torvalds
2006-11-05 19:04 ` Karl Hasselström
2006-11-05 19:29 ` Jakub Narebski
2006-11-06 7:45 ` [PATCH] Add a MIME-Version header to e-mails Karl Hasselström
2006-11-06 7:56 ` Karl Hasselström
2006-11-07 9:53 ` Catalin Marinas
2006-11-07 19:09 ` Catalin Marinas [this message]
2006-11-08 8:40 ` Karl Hasselström
2006-11-08 9:41 ` Catalin Marinas
2006-11-08 10:01 ` Karl Hasselström
2006-11-08 10:12 ` Catalin Marinas
2006-11-12 21:14 ` [StGIT PATCH 0/2] mail and import tests Karl Hasselström
2006-11-12 21:15 ` [StGIT PATCH 1/2] Regression test for "stg import" Karl Hasselström
2006-11-12 21:15 ` [StGIT PATCH 2/2] Regression test for "stg mail" Karl Hasselström
2006-11-11 12:24 ` [PATCH] Add a MIME-Version header to e-mails Karl Hasselström
2006-11-16 17:24 ` Catalin Marinas
2006-11-03 12:44 ` [PATCH] Allow hand-editing of patches before sending Catalin Marinas
2006-11-03 13:02 ` Karl Hasselström
2006-11-03 13:16 ` Catalin Marinas
2006-11-03 13:25 ` Karl Hasselström
2006-11-03 13:25 ` Catalin Marinas
2006-11-03 13:33 ` Karl Hasselström
2006-11-03 13:42 ` Karl Hasselström
2006-11-03 13:56 ` Catalin Marinas
2006-11-03 14:37 ` Catalin Marinas
2006-11-03 13:39 ` Petr Baudis
2006-11-03 14:01 ` Catalin Marinas
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=b0943d9e0611071109w584f4f7fv3ba1b7dbd9413717@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).