From: Junio C Hamano <junkio@cox.net>
To: "Brown, Len" <len.brown@intel.com>
Cc: <git@vger.kernel.org>
Subject: Re: git-send-email vs address syntax
Date: Wed, 02 May 2007 23:25:33 -0700 [thread overview]
Message-ID: <7v8xc62zky.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB6030BDEAF@hdsmsx411.amr.corp.intel.com> (Len Brown's message of "Thu, 3 May 2007 02:13:18 -0400")
"Brown, Len" <len.brown@intel.com> writes:
> I don't know if the fix should be in the git-am script
> which set the From: field, or in the git-format-patch
> script which takes that field and makes it into
> an e-mail message.
The fix should be in send-email script, as COMMITTER_NAME and
AUTHOR_NAME are just simple strings without RFC2822 limitation
(such as necessity of quoting a ".").
As a matter of fact, recent enough send-email is supposed to
have a fix for this exact problem. If your copy of send-email
does not have
sub sanitize_address_rfc822 {
you might want to upgrade. Both 1.5.2-rc1 and 1.5.1.3 have
this.
next prev parent reply other threads:[~2007-05-03 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 6:13 git-send-email vs address syntax Brown, Len
2007-05-03 6:25 ` Junio C Hamano [this message]
2007-05-03 6:30 ` Brown, Len
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=7v8xc62zky.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=len.brown@intel.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