public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Paul Bolle <pebolle@tiscali.nl>,
	Jani Nikula <jani.nikula@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	daniel@ffwll.ch, airlied@gmail.com, akpm@linux-foundation.org
Subject: Re: [RFC PATCH] get_maintainer: Look for arbitrary letter prefixes in sections
Date: Thu, 03 Nov 2016 02:16:40 -0700	[thread overview]
Message-ID: <1478164600.1924.18.camel@perches.com> (raw)
In-Reply-To: <1478164043.1911.6.camel@tiscali.nl>

On Thu, 2016-11-03 at 10:07 +0100, Paul Bolle wrote:
> On Mon, 2016-10-24 at 11:05 -0700, Joe Perches wrote:
> > Jani Nikula proposes patches to add a few new letter prefixes
> > for "B:" bug reporting and "C:" maintainer chatting to the
> > various sections of MAINTAINERS.
> > 
> > Add a generic mechanism to get_maintainer.pl to find sections that
> > have any combination of "[A-Z]" letter prefix types in a section.
> > 
> > Signed-off-by: Joe Perches <joe@perches.com>
> 
> This patch made it into linux-next (ie, next-20161028).
> 
> > --- a/scripts/get_maintainer.pl
> > +++ b/scripts/get_maintainer.pl
> > @@ -271,7 +273,8 @@ $output_multiline = 0 if ($output_separator ne ", ");
> >  $output_rolestats = 1 if ($interactive);
> >  $output_roles = 1 if ($output_rolestats);
> >  
> > -if ($sections) {
> > +if ($sections || $letters ne "") {
> > +    $sections = 1;
> 
> This triggers:
>     Unrecognized character \xA0; marked by <-- HERE after <-- HERE near column 1 at ./scripts/get_maintainer.pl line 277.
> 
> Git blame shows:
>     git blame -L 277,+1 ./scripts/get_maintainer.pl
>     b67071653d3fc (Joe Perches 2016-10-28 13:22:01 +1100 277) <A0><A0><A0><A0>$sections = 1;
> 
> (A0 seems to be the no break space. That character was inserted more
> often further down the patch.)
> 
> Anybody else seeing this?

Yes, it's been reported and should be fixed in -mm.
The fix should show up in -next in a little bit.

For now, try:
$ sed -i -e 's/\xA0/ /g' scripts/get_maintainer.pl

cheers, Joe

  reply	other threads:[~2016-11-03  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 12:22 [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs Jani Nikula
2016-10-20 12:22 ` [PATCH 2/4] MAINTAINERS: add drm and drm/i915 bug filing info Jani Nikula
2016-10-20 12:22 ` [PATCH 3/4] MAINTAINERS: Add "C:" for URI for chat where developers hang out Jani Nikula
2016-10-20 12:22 ` [PATCH 4/4] MAINTAINERS: add drm and drm/i915 irc channels Jani Nikula
2016-10-24  8:31 ` [PATCH 1/4] MAINTAINERS: Add "B:" for URI where to file bugs Daniel Vetter
2016-10-24  8:48 ` Andrew Donnellan
2016-10-24 18:05 ` [RFC PATCH] get_maintainer: Look for arbitrary letter prefixes in sections Joe Perches
2016-11-03  9:07   ` Paul Bolle
2016-11-03  9:16     ` Joe Perches [this message]
2016-11-03  9:18       ` Paul Bolle

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=1478164600.1924.18.camel@perches.com \
    --to=joe@perches.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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