mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] parse-maintainers: Add ability to specify filenames
Date: Fri, 11 Aug 2017 03:02:41 -0700	[thread overview]
Message-ID: <1502445761.3099.8.camel@perches.com> (raw)
In-Reply-To: <48703c068b3235223ffa3b2eb268fa0a125b25e0.1502251549.git.joe@perches.com>

On Tue, 2017-08-08 at 21:06 -0700, Joe Perches wrote:
> parse-maintainers.pl is convenient, but currently hard-code the
> filenames that are used.
> 
> Allow user-specified filenames to simplify the use of the script.
> 
> Miscellanea:
> 
> o Change the file permissions to 755 to the script is executable

Hey Linus.

Andrew picked this up, but his quilt based tools to not
keep the file permission change.

Could you pick this up instead please?

It could be useful if/when the MAINTAINERS file is split
and when the individual files need to be realphabetized.

Thanks.

> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  scripts/parse-maintainers.pl | 52 +++++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 47 insertions(+), 5 deletions(-)
>  mode change 100644 => 100755 scripts/parse-maintainers.pl
> 
> diff --git a/scripts/parse-maintainers.pl b/scripts/parse-maintainers.pl
> old mode 100644
> new mode 100755
> index e40b53db7f9f..4499cefce348
> --- a/scripts/parse-maintainers.pl
> +++ b/scripts/parse-maintainers.pl
> @@ -1,9 +1,44 @@
>  #!/usr/bin/perl -w
>  
>  use strict;
> +use Getopt::Long qw(:config no_auto_abbrev);
> +
> +my $input_file = "MAINTAINERS";
> +my $output_file = "MAINTAINERS.new";
> +my $output_section = "SECTION.new";
> +my $help = 0;
>  
>  my $P = $0;
>  
> +if (!GetOptions(
> +		'input=s' => \$input_file,
> +		'output=s' => \$output_file,
> +		'section=s' => \$output_section,
> +		'h|help|usage' => \$help,
> +	    )) {
> +    die "$P: invalid argument - use --help if necessary\n";
> +}
> +
> +if ($help != 0) {
> +    usage();
> +    exit 0;
> +}
> +
> +sub usage {
> +    print <<EOT;
> +usage: $P [options] <pattern matching regexes>
> +
> +  --input => MAINTAINERS file to read (default: MAINTAINERS)
> +  --output => sorted MAINTAINERS file to write (default: MAINTAINERS.new)
> +  --section => new sorted MAINTAINERS file to write to (default: SECTION.new)
> +
> +If <pattern match regexes> exist, then the sections that match the
> +regexes are not written to the output file but are written to the
> +section file.
> +
> +EOT
> +}
> +
>  # sort comparison functions
>  sub by_category($$) {
>      my ($a, $b) = @_;
> @@ -55,13 +90,20 @@ sub trim {
>  sub alpha_output {
>      my ($hashref, $filename) = (@_);
>  
> +    return if ! scalar(keys %$hashref);
> +
>      open(my $file, '>', "$filename") or die "$P: $filename: open failed - $!\n";
> +    my $separator;
>      foreach my $key (sort by_category keys %$hashref) {
>  	if ($key eq " ") {
> -	    chomp $$hashref{$key};
>  	    print $file $$hashref{$key};
>  	} else {
> -	    print $file "\n" . $key . "\n";
> +	    if (! defined $separator) {
> +		$separator = "\n";
> +	    } else {
> +		print $file $separator;
> +	    }
> +	    print $file $key . "\n";
>  	    foreach my $pattern (sort by_pattern split('\n', %$hashref{$key})) {
>  		print $file ($pattern . "\n");
>  	    }
> @@ -111,7 +153,7 @@ sub file_input {
>  my %hash;
>  my %new_hash;
>  
> -file_input(\%hash, "MAINTAINERS");
> +file_input(\%hash, $input_file);
>  
>  foreach my $type (@ARGV) {
>      foreach my $key (keys %hash) {
> @@ -122,7 +164,7 @@ foreach my $type (@ARGV) {
>      }
>  }
>  
> -alpha_output(\%hash, "MAINTAINERS.new");
> -alpha_output(\%new_hash, "SECTION.new");
> +alpha_output(\%hash, $output_file);
> +alpha_output(\%new_hash, $output_section);
>  
>  exit(0);

      reply	other threads:[~2017-08-11 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  4:06 Joe Perches
2017-08-11 10:02 ` Joe Perches [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=1502445761.3099.8.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome