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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2c0942db0708131009y6f1c4cc4n59d8b36943643955@mail.gmail.com>
Date:	Mon, 13 Aug 2007 10:09:08 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
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

On 8/12/07, Joe Perches <joe@...ches.com> wrote:
> I grew weary of looking up the appropriate
> maintainer email address(es) to CC: for a patch.
>
> I added flags to the MAINTAINERS file
>
> F:      file pattern
>
> for each maintained block and a script to parse
> the modified blocks for maintainer and list
> email addresses.

Why not parse git annotate or blame instead (other than it's freakin'
slow)? Using the repository history has the added benefit of telling
you a lot more fine-grained detail about who may want to know about
your 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/