public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] patman dies cryptially when a (valid) e-mail address contains parentheses (or is UTF-8)
Date: Thu, 28 Jan 2016 07:19:59 +0100	[thread overview]
Message-ID: <20160128071959.741efe8d@lilith> (raw)
In-Reply-To: <CAPnjgZ3Ep81MzczGimaTbV-ynCg-3L+HT+Kujj8hchJFN+Jpyw@mail.gmail.com>

Hello Simon,

On Wed, 27 Jan 2016 15:53:45 -0700, Simon Glass <sjg@chromium.org>
wrote:
> Hi Albert,
> 
> On 27 January 2016 at 01:22, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
> > Hello Simon,
> >
> > I just noticed this while adding a Series-cc to my work address which
> > has parentheses: running patman (without -n) will result in
> >
> >         sh: 1: Syntax error: "(" unexpected
> >
> > Which initially left me wondering what was happening until I realized
> > one of the Series-cc addresses had parentheses, e.g.
> >
> >         Series-cc: "Name NAME (NAME)" <address@domain.tld>
> >
> > Note that the parentheses were in the free-form part of the address,
> > itself within double quotation marks, which appears valid wrt the RFC.
> >
> > I've tried using single quotes as a workaround:
> >
> >         Series-cc: 'Name NAME (NAME)' <address@domain.tld>
> >
> > It kind-of-works in that patman does not die, but the resulting address
> > in the mail has outer double quotes and inner single quotes, e.g.
> >
> >         "'Name NAME (NAME)'" <address@domain.tld>
> >
> > Aditionally, addresses with names in UTF-8 also fail, though
> > differently but still with a message somewhat unrelated to the actual
> > cause (UTF-8-name is the placeholder for a name containing UTF-8
> > diacritics):
> >
> >         fatal: ambiguous argument 'UTF-8-name <addres@domain.tld>':
> >         unknown revision or path not in the working tree.
> >         Use '--' to separate paths from revisions, like this:
> >         'git <command> [<revision>...] -- [<file>...]'
> >
> > The same single-quote hack works it around, with the resulting
> > mail Cc:ing the name surrounded by single quotes only:
> >
> >         Cc: 'UTF-8-name' <addres@domain.tld>
> >
> > Cc:ing Marek who is a die-hard fan of UTF-8 names in e-mail
> > addresses. :)
> 
> I wonder if this is a problem with the cc_cmd code in patman.py?
> 
> # Called from git with a patch filename as argument
> # Printout a list of additional CC recipients for this patch
> elif options.cc_cmd:
> 
> Perhaps it should quote its output somehow?

I'll try and test that this week-end.

> Regards,
> Simon

Amicalement,
-- 
Albert.

      reply	other threads:[~2016-01-28  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  8:22 [U-Boot] patman dies cryptially when a (valid) e-mail address contains parentheses (or is UTF-8) Albert ARIBAUD
2016-01-27 22:53 ` Simon Glass
2016-01-28  6:19   ` Albert ARIBAUD [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=20160128071959.741efe8d@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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