From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
joe@perches.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Eng.Linux@digi.com
Subject: Re: [PATCH] [154/2many] MAINTAINERS - DIGI INTL. EPCA DRIVER
Date: Mon, 13 Aug 2007 09:15:06 -0700 [thread overview]
Message-ID: <46C0838A.2030504@intel.com> (raw)
In-Reply-To: <46C06E70.9090905@s5r6.in-berlin.de>
Stefan Richter wrote:
> Alan Cox wrote:
>> On Sun, 12 Aug 2007 23:26:16 -0700
>> joe@perches.com wrote:
>>> DIGI INTL. EPCA DRIVER
>>> -P: Digi International, Inc
>>> +P: Digi International Inc
>> The "," is correct and how they added themselves.
>>
>> Please don't hide other types of change in a large changeset without
>> notice, thats not good
>>
>> NAK
>
> I'm not Joe, but I gather this change is in order to support generation
> of RFC 278 headers by the proposed script.
>
> However, rather than mangle entries in MAINTAINERS for the script, I
> suggest that the script is enhanced instead. Simplest solution: If the
> script finds punctuation and other problematic characters in the P:
> field, simply omit that part from the e-mail address.
or properly put it on "quotes":
Cc: "Digi International, Inc" <foo@bar.com>
is perfectly valid.
Auke
next prev parent reply other threads:[~2007-08-13 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:26 [PATCH] [154/2many] MAINTAINERS - DIGI INTL. EPCA DRIVER joe
2007-08-13 10:53 ` Alan Cox
2007-08-13 14:45 ` Stefan Richter
2007-08-13 15:35 ` Alan Cox
2007-08-13 16:15 ` Kok, Auke [this message]
2007-08-13 16:35 ` Joe Perches
2007-08-14 4:13 ` Joe Perches
2007-08-14 4:29 ` Cal Peake
2007-08-14 4:39 ` Joe Perches
2007-08-14 4:52 ` Cal Peake
2007-08-14 20:38 ` Stefan Richter
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=46C0838A.2030504@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=Eng.Linux@digi.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.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