Re: [char-misc-next] mei: request async autosuspend at the end of enumeration

From: Jakub NarÄbski
Date: Fri Nov 25 2016 - 15:34:11 EST

W dniu 25.11.2016 o 04:14, Jeff King pisze:
> On Thu, Nov 24, 2016 at 10:37:14PM +0000, Winkler, Tomas wrote:
>>>>> Cc: <stable@xxxxxxxxxxxxxxx> # 4.4+
>>>> Looks like git send-email is not able to parse this address correctly
>>>> though this is suggested format by Documentation/stable_kernel_rules.txt.
>>>> Create wrong address If git parsers is used : 'stable@xxxxxxxxxxxxxxx#4.4+'

> The patch just brings parity to the Mail::Address behavior and git's
> fallback parser, so that you don't end up with the broken
> stable@xxxxxxxxxxxxxxx#4.4+ address. Instead, that content goes into the
> name part of the address.
> It sounds like you want the "# 4.4+" to be dropped entirely in the
> rfc822 header. It looks like send-email used to do that, but stopped in
> b1c8a11c8 (send-email: allow multiple emails using --cc, --to and --bcc,
> 2015-06-30).
> So perhaps there are further fixes required, but it's hard to know. The
> input isn't a valid rfc822 header, so it's not entirely clear what the
> output is supposed to be. I can buy either "drop it completely" or
> "stick it in the name field of the cc header" as reasonable.

Well, we could always convert it to email address comment, converting
for example the following trailer:

Cc: John Doe <john@xxxxxxxxxxx> # comment

to the following address:

John Doe <john@xxxxxxxxxxx> (comment)

Just FYI. Though I'm not sure how well this would work...

Jakub NarÄbski