From: Joe Perches <joe@perches.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: Add the --for-tree argument
Date: Thu, 13 Oct 2022 20:48:10 -0700 [thread overview]
Message-ID: <3251b73cce77964413e01d4f5361de48942e98ae.camel@perches.com> (raw)
In-Reply-To: <mhng-220de489-6329-41ce-9a6f-d7acdd73344c@palmer-ri-x1c9a>
On Thu, 2022-10-13 at 19:56 -0700, Palmer Dabbelt wrote:
> On Thu, 13 Oct 2022 17:39:53 PDT (-0700), joe@perches.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@brainfault.org> (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
> > > kvm@vger.kernel.org (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
> > > kvm-riscv@lists.infradead.org (maintainer:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv))
> > > linux-riscv@lists.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.
Thanks, Joe
next prev parent reply other threads:[~2022-10-14 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 21:57 Palmer Dabbelt
2022-10-14 0:39 ` Joe Perches
2022-10-14 2:56 ` Palmer Dabbelt
2022-10-14 3:48 ` Joe Perches [this message]
2022-10-14 3:52 ` Palmer Dabbelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3251b73cce77964413e01d4f5361de48942e98ae.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®