git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-send-email.perl: Add angle brackets to In-Reply-To if necessary
Date: Sun, 12 Aug 2007 14:49:01 +0200	[thread overview]
Message-ID: <20070812124901.GA9662@informatik.uni-freiburg.de> (raw)
In-Reply-To: <85lkchqixk.fsf@lola.goethe.zz>

Hello David,

> I have not actually tested this, but from staring at it intensively,
> it should be correct.  One of the things that bit me when I tried
> using this program.
> 
> ...
> -	$initial_reply_to =~ s/(^\s+|\s+$)//g;
> +	$initial_reply_to =~ s/^\s+<?/</;
> +	$initial_reply_to =~ s/>?\s+$/>/;
> ...

some rules from rfc822:

	optional-field	= ... / "In-Reply-To:"  *(phrase / msg-id) / ...
	msg-id		= "<" addr-spec ">"
	phrase		= 1*word
	word		= atom / quoted-string
	atom		= 1*<any CHAR except specials, SPACE and CTLs>
	quoted-string	= <"> *(qtext/quoted-pair) <">
	...

With 1*... meaning "one or more" and *... meaning "zero or more".

That is not all fields of In-Reply-To: must be enclosed in '<', '>'.  I
didn't know that before looking it up and I expect it's not very common.
Even if no "phrase" is used there can be multiple msg-id's and then your
patch doesn't do the right thing.

But anyhow I think it's bearable to include these angle brackets in the
cut-and-paste process.

Best regards
Uwe

-- 
Uwe Kleine-König

http://www.google.com/search?q=1+electron+mass%3D

      reply	other threads:[~2007-08-12 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12  8:02 [PATCH] git-send-email.perl: Add angle brackets to In-Reply-To if necessary David Kastrup
2007-08-12 12:49 ` Uwe Kleine-König [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=20070812124901.GA9662@informatik.uni-freiburg.de \
    --to=ukleinek@informatik.uni-freiburg.de \
    --cc=dak@gnu.org \
    --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).