Re: [PATCH] git-send-email.perl: Add angle brackets to In-Reply-To if necessary

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jeff,

Jeff King wrote:
> On Thu, Sep 13, 2007 at 02:39:57PM +0200, Uwe Kleine-König wrote:
> 
> > > > message-id's are defined to have the angle brackets.
> > >   Yes, it's definitive, not having the < > is wrong as per RFC.
> > Which RFC do you mean here? If I read rfc822 correctly, it allows values
> > that are not enclosed in angle brackets.
> 
> RFC 822, section 4.1 ("Syntax", bottom of page 18):
> 
>      msg-id      =  "<" addr-spec ">"            ; Unique message id
right, but RFC 822 also has on page 18:

	optional-field = ... / "In-Reply-To" ":" *(phrase / msg-id)

and if you take the phrase branch, it doesn't need to be enclosed in
angle brackets.  Moreover the * means "zero or more of".

> 2822 contains similar BNF.
Ah, RFC 2822 has:

	in-reply-to     =       "In-Reply-To:" 1*msg-id CRLF
	msg-id          =       [CFWS] "<" id-left "@" id-right ">" [CFWS]

So there is no phrase branch any more, but still you can reference more
than one id.

Moreover RFC 2822 has a description of the (now obsolete) "phrase"s in
"In-Reply-To:" in chapter 4.5.4.

Best regards
Uwe

-- 
Uwe Kleine-König

Set the I_WANT_A_BROKEN_PS environment variable to force BSD syntax ...
	-- manpage of procps
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux