From: David Woodhouse <dwmw2@infradead.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Features ask for git-send-email
Date: Tue, 02 May 2006 15:14:15 +0100 [thread overview]
Message-ID: <1146579255.17934.8.camel@pmac.infradead.org> (raw)
In-Reply-To: <e37km0$vav$1@sea.gmane.org>
On Tue, 2006-05-02 at 14:53 +0200, Jakub Narebski wrote:
> Doesn't
> Content-Type: text/plain; charset=$charset
> header need also
> MIME-Version: 1.0
Maybe. The use of Content-Type: actually predates RFC2045, and if we
include a MIME-Version header then we should make 100% sure that we also
conform to the rest of RFC2045, which I hadn't actually looked at. In
particular, we should take care of Content-Transfer-Encoding.
I'd prefer to leave MIME-Version out for now, I think.
--
dwmw2
next prev parent reply other threads:[~2006-05-02 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 13:30 Features ask for git-send-email Bertrand Jacquin
2006-05-02 12:36 ` David Woodhouse
2006-05-02 12:53 ` Jakub Narebski
2006-05-02 14:14 ` David Woodhouse [this message]
2006-05-02 15:35 ` Jakub Narebski
2006-05-02 22:46 ` Bertrand Jacquin
2006-05-02 23:33 ` David Woodhouse
2006-05-02 23:51 ` Bertrand Jacquin
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=1146579255.17934.8.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).