public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Greg KH <greg@kroah.com>
Cc: Harry Wei <jiaweiwei.xiyou@gmail.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	davem@davemloft.net, rdunlap@xenotime.net, trivial@kernel.org
Subject: Re: MAINTAINERS: a question about it
Date: Sat, 12 Feb 2011 00:43:44 +0100	[thread overview]
Message-ID: <20110212004344.0c531989@schatten.dmk.lab> (raw)
In-Reply-To: <20110211212554.GA11175@kroah.com>

On Fri, 11 Feb 2011 13:25:54 -0800
Greg KH <greg@kroah.com> wrote:

> On Fri, Feb 11, 2011 at 10:14:33PM +0100, Florian Mickler wrote:
> > On Fri, 11 Feb 2011 07:40:14 -0800
> > Greg KH <greg@kroah.com> wrote:
> > 
> > > On Fri, Feb 11, 2011 at 08:29:28PM +0800, Harry Wei wrote:
> > > > Hi us,
> > > >      I saw MAINTAINERS these days. I find we should program a script(shell) for checking if a maintainer added himself in correct position. 
> > > >      Because the MAINTAINERS is in alphabetical order and it has lots of maintainers now.
> > > >      I just want to ask if anyone is doing this work. If it has  been began i will do other things about kernel. If not, i will program this script(shell) for us.
> > > 
> > > Why not just modify the 'scripts/get_maintainers.pl' tool to do this?
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > surely, you mean hooking it into 'scripts/checkpatch.pl' ?
> > 
> 
> No, I hadn't ment that, as I figured get_maintainers.pl already parsed
> the MAINTAINERS file, so it might be easier to do it there.

perl -e '$last = "0"; while (<>) { @F = split(/:/); if ($begin) { if (!/^\s*$/ && length($F[0]) > 1) { unless ($last le $_) { print "header wrongly sorted! ($_)\n"; $err =1; } $last = $_; }}; $begin = 1 if ( $F[0] =~ /\t\t-----------------------------------$/);} exit(1) if ($err); ' < MAINTAINERS

:)

Regards,
Flo

  reply	other threads:[~2011-02-11 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 12:29 MAINTAINERS: a question about it Harry Wei
2011-02-11 15:40 ` Greg KH
2011-02-11 21:14   ` Florian Mickler
2011-02-11 21:25     ` Greg KH
2011-02-11 23:43       ` Florian Mickler [this message]
     [not found]         ` <AANLkTikXxf8BDmf5gfOQ6T0OvR=_RUFdOiYEPZVJ2Pm2@mail.gmail.com>
     [not found]           ` <20110212140158.00c7faa3@schatten.dmk.lab>
     [not found]             ` <AANLkTikbS9dWOpw-sUKFV01mnMBrQof0rQO6sde+53qe@mail.gmail.com>
2011-02-12 13:29               ` Fwd: " Harry Wei

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=20110212004344.0c531989@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=jiaweiwei.xiyou@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=trivial@kernel.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