linux-kernel - Re: [PATCH] get_maintainer: Add the --for-tree argument

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]

Date:   Thu, 13 Oct 2022 20:52:56 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...osinc.com>
To:     joe@...ches.com
CC:     linux-kernel@...r.kernel.org
Subject:     Re: [PATCH] get_maintainer: Add the --for-tree argument

On Thu, 13 Oct 2022 20:48:10 PDT (-0700), joe@...ches.com wrote:
> On Thu, 2022-10-13 at 19:56 -0700, Palmer Dabbelt wrote:
>> On Thu, 13 Oct 2022 17:39:53 PDT (-0700), joe@...ches.com wrote:
>> > On Thu, 2022-10-13 at 14:57 -0700, Palmer Dabbelt wrote:
>> > > I recently wanted to look up the maintainers for each tree path via a
>> > > script, and I couldn't find a better way to do that than poking
>> > > get_maintainer.pl to add a new argument.  This lets folks run something
>> > > like
>> > > 
>> > >     $ ./scripts/get_maintainer.pl --for-tree git://github.com/kvm-riscv/linux.git
>> > >     Anup Patel <anup@...infault.org> (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
>> > >     kvm@...r.kernel.org (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
>> > >     kvm-riscv@...ts.infradead.org (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
>> > >     linux-riscv@...ts.infradead.org (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
>> > > 
>> > > to find out who owns a tree.
>> > 
>> > I'm not sure this is useful.
> []
>> Generally sound like you 
>> don't want this one so I'm going to punt on fixing these for now, I 
>> don't care all that much about having this merged.
>> 
>> LMK if you want a v2, though.
>
> I think it's not necessary.

Works for me.