From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: corbet@lwn.net, josh@joshtriplett.org, kees@kernel.org,
konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
workflows@vger.kernel.org
Subject: Re: [PATCH v2 2/2] agents: add unified agent coding assistant configuration
Date: Sun, 10 Aug 2025 09:01:00 +0200 [thread overview]
Message-ID: <2025081040-armchair-although-8bf1@gregkh> (raw)
In-Reply-To: <20250809234008.1540324-3-sashal@kernel.org>
On Sat, Aug 09, 2025 at 07:40:08PM -0400, Sasha Levin wrote:
> Create a single source of truth for agent instructions with
> symlinks for all major coding agents:
> - CLAUDE.md (Claude Code)
> - .github/copilot-instructions.md (GitHub Copilot)
> - .cursorrules (Cursor)
> - .codeium/instructions.md (Codeium)
> - .continue/context.md (Continue)
> - .windsurfrules (Windsurf)
> - GEMINI.md (Gemini)
Having these non-dot-files in the root directory for just specific
closed source tools feels a bit wrong to me. I thought all of these
tools were standardizing on "use README" and didn't need these extra
helpers? The fact that most of them just contain README seems like
that's the case, they just need to work it out somehow?
Anyway, I'd not like this patch to be added (patch 1/2 is great), as it
feels like these agents need to get their act together in ways to not
need these, we shouldn't be forced to deal with their inefficiencies.
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-10 7:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 23:40 [PATCH v2 0/2] Add unified configuration for coding agents Sasha Levin
2025-08-09 23:40 ` [PATCH v2 1/2] README: restructure with role-based documentation and guidelines Sasha Levin
2025-08-10 15:44 ` Joe Perches
2025-08-10 16:46 ` Sasha Levin
2025-08-11 0:10 ` Joe Perches
2025-08-11 0:06 ` Randy Dunlap
2025-08-11 8:22 ` Geert Uytterhoeven
2025-08-11 15:48 ` Sasha Levin
2025-08-15 6:19 ` Kees Cook
2025-08-09 23:40 ` [PATCH v2 2/2] agents: add unified agent coding assistant configuration Sasha Levin
2025-08-10 7:01 ` Greg KH [this message]
2025-08-10 14:22 ` Sasha Levin
2025-08-14 0:36 ` Steven Rostedt
2025-08-15 6:23 ` Kees Cook
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=2025081040-armchair-although-8bf1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--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