From: "Philippe Bruhat (BooK)" <book@cpan.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] mailinfo: better parse email adresses containg parentheses
Date: Tue, 22 Jul 2008 12:24:39 +0200 [thread overview]
Message-ID: <20080722102439.GB7792@plop> (raw)
In-Reply-To: <7v63qyr4kk.fsf@gitster.siamese.dyndns.org>
On Mon, Jul 21, 2008 at 08:16:43PM -0700, Junio C Hamano wrote:
> >
> > Signed-off-by: Philippe Bruhat (BooK) <book@cpan.org>
>
> Hmm, tests?
>
> By the way, that second form parses like this:
>
> mailbox =
> name-addr =
> display-name angle-addr = "User Name (me) <user@host>"
>
> display-name =
> phrase = "User Name"
>
> angle-addr = CFWS "<" addr-spec ">" = "(me) <user@host>"
>
> So strictly speaking, shouldn't we be stripping the whole (me) as garbage?
> It is not even part of the display-name but is a whitespace equivalent
> comment.
Well, I use this:
"Philippe Bruhat (BooK)" <book@cpan.org>
as my From: line, and I would like to be able to use it so in git.
As git knows the difference between user name and user email, it should
be able to keep the information separate all the way.
Which makes me think that since it seems that rebase goes through a
patch-file step, the problem with my username may actually lie with
creating the patch file (no quotes around a user name containing parens)
rather than with parsing the patch From: line.
--
Philippe Bruhat (BooK)
Everyone's life seems easier from the outside.
(Moral from Groo The Wanderer #45 (Epic))
prev parent reply other threads:[~2008-07-22 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 13:34 [PATCH] mailinfo: better parse email adresses containg parentheses Philippe Bruhat (BooK)
2008-07-21 14:36 ` Lukas Sandström
2008-07-22 3:16 ` Junio C Hamano
2008-07-22 10:24 ` Philippe Bruhat (BooK) [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=20080722102439.GB7792@plop \
--to=book@cpan.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).