From: Jonathan Corbet <corbet@lwn.net>
To: WangYuli <wangyuli@uniontech.com>,
masahiroy@kernel.org, ojeda@kernel.org, nathan@kernel.org,
alan.maguire@oracle.com, laurent.pinchart@ideasonboard.com,
kris.van.hees@oracle.com, linux@weissschuh.net, tamird@gmail.com,
vegard.nossum@oracle.com, ardb@kernel.org,
mchehab+huawei@kernel.org, lizhijian@fujitsu.com
Cc: linux-kernel@vger.kernel.org, zhanjun@uniontech.com,
niecheng1@uniontech.com, guanwentao@uniontech.com,
WangYuli <wangyuli@uniontech.com>
Subject: Re: [PATCH] gitignore: allow .pylintrc to be tracked
Date: Wed, 02 Jul 2025 17:10:44 -0600 [thread overview]
Message-ID: <87pleimbnv.fsf@trenco.lwn.net> (raw)
In-Reply-To: <1A357750FF71847E+20250623071933.311947-1-wangyuli@uniontech.com>
WangYuli <wangyuli@uniontech.com> writes:
> The .pylintrc file was introduced by commit 02df8e3b333c ("docs: add a
> .pylintrc file with sys path for docs scripts") to provide Python path
> configuration for documentation scripts. However, the generic ".*" rule
> in .gitignore causes this tracked file to be ignored, leading to warnings
> during kernel builds.
>
> Add !.pylintrc to the exception list to explicitly allow this
> configuration file to be tracked by git, consistent with other
> development tool configuration files like .clang-format and .rustfmt.toml.
>
> This resolves the build warning:
> .pylintrc: warning: ignored by one of the .gitignore files
>
> Fixes: 02df8e3b333c ("docs: add a .pylintrc file with sys path for docs scripts")
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
jon
prev parent reply other threads:[~2025-07-02 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 7:19 [PATCH] gitignore: allow .pylintrc to be tracked WangYuli
2025-06-23 8:08 ` Miguel Ojeda
2025-06-23 18:25 ` Mauro Carvalho Chehab
2025-07-02 23:10 ` Jonathan Corbet [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=87pleimbnv.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alan.maguire@oracle.com \
--cc=ardb@kernel.org \
--cc=guanwentao@uniontech.com \
--cc=kris.van.hees@oracle.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lizhijian@fujitsu.com \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nathan@kernel.org \
--cc=niecheng1@uniontech.com \
--cc=ojeda@kernel.org \
--cc=tamird@gmail.com \
--cc=vegard.nossum@oracle.com \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.