From: David Woodhouse <dwmw2@infradead.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Len Brown <lenb@kernel.org>, git@vger.kernel.org
Subject: Re: git-send-email w/ headers
Date: Fri, 06 Oct 2006 17:52:10 +0100 [thread overview]
Message-ID: <1160153530.4795.51.camel@pmac.infradead.org> (raw)
In-Reply-To: <7viriy9w1q.fsf@assigned-by-dhcp.cox.net>
On Thu, 2006-10-05 at 16:34 -0700, Junio C Hamano wrote:
> Len Brown <len.brown@intel.com> writes:
>
> > git-send-email seems to strip out my custom headers.
>
> It seems to not care about anything but a selected few.
>
> Could you give this a try, please?
It also needs to preserve (and indeed to provide by default)
Content-Type headers to specify the character set.
--
dwmw2
prev parent reply other threads:[~2006-10-06 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 16:50 git-send-email w/ headers Len Brown
2006-10-05 23:34 ` Junio C Hamano
2006-10-06 4:41 ` Len Brown
2006-10-06 6:09 ` Junio C Hamano
2006-10-07 4:40 ` Len Brown
2006-10-06 16:52 ` David Woodhouse [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=1160153530.4795.51.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=lenb@kernel.org \
/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).