From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-am: "Patch fragment without a header"
Date: Mon, 06 Feb 2006 19:32:18 -0800 [thread overview]
Message-ID: <43E814C2.6090104@zytor.com> (raw)
In-Reply-To: <7vwtg73ld7.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> Linus would have said "Say No to MIME". I am a bit too busy
> right now so if you are inclined to take a look, the problem is
> in mailinfo.
>
Unfortunately git-mailinfo is in C, otherwise I'd have suggested using
the Perl MIME-tools, which seems to have all this stuff in it.
It might just be easier to try to rewrite git-mailinfo in Perl...
-hpa
next prev parent reply other threads:[~2006-02-07 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 2:59 git-am: "Patch fragment without a header" H. Peter Anvin
2006-02-07 3:20 ` Junio C Hamano
2006-02-07 3:32 ` H. Peter Anvin [this message]
2006-02-07 5:35 ` Junio C Hamano
2006-02-07 15:46 ` Linus Torvalds
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E814C2.6090104@zytor.com \
--to=hpa@zytor.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).