From: Randy Dunlap <rdunlap@xenotime.net>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Cruz Julian Bishop <cruzjbishop@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Quick question: Maintainers for scripts
Date: Sun, 21 Oct 2012 18:44:21 -0700 [thread overview]
Message-ID: <5084A4F5.4030509@xenotime.net> (raw)
In-Reply-To: <CAM_iQpVMzYufF71jKOhbKh9r=PaEgJdSZeRs_Z9fzyv4E4e+Wg@mail.gmail.com>
On 10/21/2012 06:37 PM, Cong Wang wrote:
> On Mon, Oct 22, 2012 at 6:35 AM, Cruz Julian Bishop
> <cruzjbishop@gmail.com> wrote:
>> Hi everyone,
>>
>> I was just wondering - Since (last time I looked, anyway),
>> /scripts/* has no maintainer, who would I send patches to?
>>
>> Would I just send them to the mailing list, or is there a
>> sort of catch-all maintainer for things like this?
>>
>
> linux-kbuild@vger.kernel.org
That is probably the best single answer.
An alternative is to run ./scripts/get_maintainer.pl -f $filename
on each file in scripts. That will give you more explicit and more
correct answers.
--
~Randy
prev parent reply other threads:[~2012-10-22 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 22:35 Cruz Julian Bishop
2012-10-22 1:37 ` Cong Wang
2012-10-22 1:44 ` Randy Dunlap [this message]
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=5084A4F5.4030509@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=cruzjbishop@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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
Powered by JetHome