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: Thu, 16 Nov 2006 17:24:01 +0000 [thread overview]
Message-ID: <b0943d9e0611160924s55383480x68832ef0a6183780@mail.gmail.com> (raw)
In-Reply-To: <20061111122403.GC11224@diana.vm.bytemark.co.uk>
On 11/11/06, Karl Hasselström <kha@treskal.com> wrote:
> One potentially hazardous thing: you encode the mail before letting
> the user edit it (with the -e and -E switches). This means that the
> user can insert non-ascii characters in the body after you've already
> decided it's safe to use 7bit encoding. It also means that the user
> must be careful to rfc2047-encode any changes to the Subject: and
> From: headers.
I changed this to edit the mail before encoding it. You can no longer
see the full headers (those added by StGIT) but even in a normal
e-mail client you can only see the whole headers after sending it (and
if you receive it back).
--
next prev parent reply other threads:[~2006-11-16 17:24 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
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 [this message]
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=b0943d9e0611160924s55383480x68832ef0a6183780@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).