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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 04 Jul 2008 16:08:30 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com>
Cc:	Oliver Neukum <oliver@...kum.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [RFC] MAINTAINERS service, was: Re: alphabetic ordering of MAINTAINERS

Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com> writes:

> Why not make that a script that parses MAINTAINERS and lives in scripts/
> and that can be used as --cc-cmd to git-send-email?  Then no service
> needs to be maintained, you don't get the observers functionality
> though.  (But that's what mailing lists are good for.)
>
> Of course MAINTAINERS needs to be modified to have the path specifiers.

Because then:
- the action is not effective immediately but sometimes after few
  months, not counting people still working with 2.6.12 or so.
- IMHO adding Cc: patch-service is a bit easier than using a script
- I think the "observers" thing is worth the effort. Now I only see
  changes to certain areas I'm interested in when they are accepted
  upstream.
- maintaining the script is probably more work than maintaining the
  database :-)

And with a service you can:
- maintain a patch archive
- be sure nobody tries to be "creative"
- perhaps other things I haven't thought about.
-- 
Krzysztof Halasa
--
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/

Powered by blists - more mailing lists