From: Joe Perches <joe@perches.com>
To: "Łukasz Stelmach" <l.stelmach@samsung.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] get_maintainer: look for configuration files in ./scripts
Date: Tue, 16 Nov 2021 15:10:21 -0800 [thread overview]
Message-ID: <6358495179b8abceafb651e58e933b8cf3a8ff1f.camel@perches.com> (raw)
In-Reply-To: <20211116213403.820336-1-l.stelmach@samsung.com>
On Tue, 2021-11-16 at 22:34 +0100, Łukasz Stelmach wrote:
> Change ".scripts" to "./scripts" as described in commit bcde44ed7d2a
> ("scripts/get_maintainer.pl: use .get_maintainer.conf from . then $HOME
> then scripts").
The intent there was to use the <kernel_tree>/scripts directory
Adding . to that would change that.
next prev parent reply other threads:[~2021-11-16 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211116213417eucas1p2a9679f03f7945f7c2bdfcba7a4e7c405@eucas1p2.samsung.com>
2021-11-16 21:34 ` Łukasz Stelmach
[not found] ` <CGME20211116213417eucas1p133783708f01c8cf82bd341a4cf95a833@eucas1p1.samsung.com>
2021-11-16 21:34 ` [PATCH 2/2] get_maintainer: ignore "my" e-mail address Łukasz Stelmach
2021-11-16 23:14 ` Joe Perches
[not found] ` <CGME20211125161420eucas1p2b3dbac252dab05d0a5406d0fca8ab945@eucas1p2.samsung.com>
2021-11-25 16:14 ` Lukasz Stelmach
2021-11-25 16:33 ` Joe Perches
2021-11-25 17:01 ` Joe Perches
[not found] ` <CGME20211129214755eucas1p1c5ded52cda8d495d23dae59a871b9276@eucas1p1.samsung.com>
2021-11-29 21:47 ` Lukasz Stelmach
2021-11-16 21:56 ` [PATCH 1/2] get_maintainer: look for configuration files in ./scripts Andrew Morton
2021-11-16 23:10 ` Joe Perches [this message]
[not found] ` <CGME20211117120811eucas1p1cdc0aa3ab93d11cebf85592d4e98f0c7@eucas1p1.samsung.com>
2021-11-17 12:07 ` Lukasz Stelmach
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=6358495179b8abceafb651e58e933b8cf3a8ff1f.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=l.stelmach@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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®