linux-kernel - Re: [PATCH] get_maintainer: Add subsystem to reviewer output

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1446052696.2757.128.camel@perches.com>
Date:	Wed, 28 Oct 2015 10:18:16 -0700
From:	Joe Perches <joe@...ches.com>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>, k.kozlowski.k@...il.com,
	wsa@...-dreams.de, linus.walleij@...aro.org,
	Sebastian Reichel <sre@...nel.org>,
	linux-kernel@...r.kernel.org, Chanwoo Choi <cw00.choi@...sung.com>,
	broonie@...nel.org, ben-linux@...ff.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] get_maintainer: Add subsystem to reviewer output

On Wed, 2015-10-28 at 17:01 +0000, Lee Jones wrote:
> It looks like I'm going to have to drop the patch where we actually
> start using the R: tag properly due to some social, emotional issues.

btw: it seems to me the thing you're looking for is the tree
to which any particular patch could or would be applied.

That can be got by using the --scm option:

	./scripts/get_maintainer.pl --scm <patch>

Only ~400 of ~1445 subsystem sections have a "T:" tree entry
so pairing the maintainer and the tree generally tells you
who is responsible for upstreaming any patch.


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