linux-kernel - Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200708131933.10125.m.kozlowski@tuxland.pl>
Date:	Mon, 13 Aug 2007 19:33:09 +0200
From:	Mariusz Kozlowski <m.kozlowski@...land.pl>
To:	Joe Perches <joe@...ches.com>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl

Hello,

	I don't recall discusion about this so here are my 3 cents:

	I like the idea. The numerous responses you got that you made a mistake
and someone else is the maintainer just prove that this kind of information would
be nice to have. Even if it is not going to be included in mainline it is still
nice to have around as a patchset or sth. Personally I often run into trouble finding
right person to CC on patches.

I get the feeling that only the maintainers themselves + a few old geeks here know
who is maintaining what (and which file) ;-) But maybe it's just me.

The rest is as people say. These ~550 patches without 'in reply to' is a nightmare.

Regards,

	Mariusz
-
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/