From: Kees Cook <kees@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Kees Cook <kees@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Steven Rostedt <rostedt@goodmis.org>,
Josh Triplett <josh@joshtriplett.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>, Fiona Behrens <me@kloenk.dev>,
Sami Tolvanen <samitolvanen@google.com>,
Gary Guo <gary@garyguo.net>,
Kris Van Hees <kris.van.hees@oracle.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Li Zhijian <lizhijian@fujitsu.com>,
Tamir Duberstein <tamird@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
workflows@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH] .gitignore: Add Coding Assistants section
Date: Thu, 14 Aug 2025 23:44:43 -0700 [thread overview]
Message-ID: <20250815064430.work.772-kees@kernel.org> (raw)
Both Claude and Gemini save locally personalized configurations in their
respective .md files and dot-directories. Since these are continuously
updated by the developer (and agent) when working on projects, these
files must be ignored, much like how we ignore the debian/ directory, etc.
Signed-off-by: Kees Cook <kees@kernel.org>
---
.gitignore | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/.gitignore b/.gitignore
index bf5ee6e01cd4..0459a44a3d64 100644
--- a/.gitignore
+++ b/.gitignore
@@ -182,3 +182,11 @@ sphinx_*/
# Rust analyzer configuration
/rust-project.json
+
+#
+# Coding assistants
+#
+/CLAUDE.md
+/.claude/
+/GEMINI.md
+/.gemini/
--
2.34.1
next reply other threads:[~2025-08-15 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 6:44 Kees Cook [this message]
2025-08-15 16:00 ` [PATCH] .gitignore: Add Coding Assistants section Tamir Duberstein
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=20250815064430.work.772-kees@kernel.org \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=josh@joshtriplett.org \
--cc=konstantin@linuxfoundation.org \
--cc=kris.van.hees@oracle.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=sashal@kernel.org \
--cc=tamird@gmail.com \
--cc=workflows@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).