From: Don Zickus <dzickus@redhat.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-mailinfo munges the patch?
Date: Thu, 29 Mar 2007 16:53:57 -0400 [thread overview]
Message-ID: <20070329205357.GF11029@redhat.com> (raw)
In-Reply-To: <7v1wj74xck.fsf@assigned-by-dhcp.cox.net>
On Thu, Mar 29, 2007 at 01:18:51PM -0700, Junio C Hamano wrote:
> I noticed that the new mailinfo when splitting a message into
> cover letter and the patch text seems to munge the patch text,
> applying the same "if content-type is not there then assume
> latin-1 and recode to utf-8" logic that is applied to the commit
> log message. That munging should not be done to the patch text,
> and it appears the current code botches it.
Ok. I see what you are saying with the old code. Sorry about that. Do
you have a sample file that I can play with to test my fix?
Cheers,
Don
next prev parent reply other threads:[~2007-03-29 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 20:18 git-mailinfo munges the patch? Junio C Hamano
2007-03-29 20:53 ` Don Zickus [this message]
2007-03-29 21:19 ` Linus Torvalds
2007-03-29 21:52 ` Don Zickus
2007-03-29 21:24 ` Junio C Hamano
2007-03-29 21:53 ` Don Zickus
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=20070329205357.GF11029@redhat.com \
--to=dzickus@redhat.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).