linux-kernel - Re: [PATCH 1/8] Add scripts/get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20081030224331.GA30814@strlen.de>
Date:	Thu, 30 Oct 2008 23:43:31 +0100
From:	Uwe Kleine-König <ukleinek@...len.de>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Joe Perches <joe@...ches.com>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, randy.dunlap@...cle.com
Subject: Re: [PATCH 1/8] Add scripts/get_maintainer.pl

Hello,

> > Also, this:
> > 
> >  MAINTAINERS | 1096 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> >  1 file changed, 1094 insertions(+), 2 deletions(-)
> > 
> > isn't practical for me or Stephen to carry, I'm afraid.  That's
> > probably the most-patched file in the kernel.  This will need to be a
> > direct you->Linus thing.
> > 
> > I think the feature is sorely needed and will prove useful.
> 
> Would you be willing to merge the scripts etc, leaving only
> MAINTAINERS file for direct merge with Linus, preferably at the -rc5
> or something?
I still think that the source files should (additionally) be parsed
somehow, too.  Something like

	/*
	 * TOPIC
	 * P: A. U. Thor <author@...mp.l.e>
	 * M: lkml@...nel.org
	 */

at the beginning of a file.  The advantage is that MAINTAINERS doesn't
need to have an entry for each driver and so the F: field cannot become
inconsistent and the author doesn't need to bother getting the entry
into MAINTAINERS---just the driver file is enough.
 
Best regards
Uwe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/