From: "Stephen R. van den Berg" <srb@cuci.nl>
To: git@vger.kernel.org
Subject: Re: RFC822 From: fields
Date: Sat, 26 Apr 2008 13:45:18 +0200 [thread overview]
Message-ID: <20080426114518.GA19558@cuci.nl> (raw)
In-Reply-To: <87r6ctatma.fsf@mid.deneb.enyo.de>
Florian Weimer wrote:
>* Stephen R. van den Berg:
>> I noticed that the From: field generated by git-format-patch does not
>> conform to RFC822 format when the realname contains a dot (like mine).
>This was fixed in RFC 2822, and the fix has already been deployed widely
>(even before the advent of RFC 2822). I don't think there's any need to
>change GIT.
True indeed. Ironically, the vger.kernel.org mailserver adheres to
RFC822 and ignores RFC2822 at the moment, which means that generating patches
from git, for the git mailinglist doesn't work without intervention.
I already contacted the vger-mailserver admin about this.
--
Sincerely, srb@cuci.nl
Stephen R. van den Berg.
prev parent reply other threads:[~2008-04-26 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 23:51 RFC822 From: fields Stephen R. van den Berg
2008-04-26 0:01 ` Junio C Hamano
2008-04-26 8:49 ` Florian Weimer
2008-04-26 11:45 ` Stephen R. van den Berg [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=20080426114518.GA19558@cuci.nl \
--to=srb@cuci.nl \
--cc=git@vger.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).