mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: commit 23cb8490c0d3 ("MAINTAINERS: fix bad file pattern")
Date: Mon, 30 Mar 2020 01:55:04 -0700	[thread overview]
Message-ID: <27fadca7455ffa95779c33e546a57ea7906a1125.camel@perches.com> (raw)
In-Reply-To: <CAHp75VfJS4hAxdq67NwAXs8U+6UzL8=bqnCEpSy45R0Gj1L8NA@mail.gmail.com>

On Mon, 2020-03-30 at 10:35 +0300, Andy Shevchenko wrote:
> On Mon, Mar 30, 2020 at 5:38 AM Joe Perches <joe@perches.com> wrote:
> >    MAINTAINERS: fix bad file pattern
> > 
> >     Testing 'parse-maintainers' due to the previous commit shows a bad file
> >     pattern for the "TI VPE/CAL DRIVERS" entry in the MAINTAINERS file.
> > 
> >     There's also a lot of mis-ordered entries, but I'm still a bit nervous
> >     about the inevitable and annoying merge problems it would probably cause
> >     to fix them up.
> 
> I'm wondering if order depends to current locale. If so, the script
> should override locale as well.

Perhaps:
---
diff --git a/scripts/parse-maintainers.pl b/scripts/parse-maintainers.pl
index 2ca4eb3..08db9b 100755
--- a/scripts/parse-maintainers.pl
+++ b/scripts/parse-maintainers.pl
@@ -3,6 +3,7 @@
 
 use strict;
 use Getopt::Long qw(:config no_auto_abbrev);
+no locale;
 
 my $input_file = "MAINTAINERS";
 my $output_file = "MAINTAINERS.new";



  reply	other threads:[~2020-03-30  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  2:35 Joe Perches
2020-03-30  7:35 ` Andy Shevchenko
2020-03-30  8:55   ` Joe Perches [this message]
2020-04-11 16:43 ` Request to sort MAINTAINERS again just before an -rc1 release Joe Perches
2020-04-12 18:08   ` Linus Torvalds
2020-04-12 19:45     ` Joe Perches

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=27fadca7455ffa95779c33e546a57ea7906a1125.camel@perches.com \
    --to=joe@perches.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --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

all inboxes | Powered by JetHome®