From: Kees Cook <kees@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
rdunlap@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add AGENTS.md as a symlink to README
Date: Thu, 24 Sep 2026 17:12:15 -0700 [thread overview]
Message-ID: <202609241709.8B710211@keescook> (raw)
In-Reply-To: <20260924134945.3095661-1-sashal@kernel.org>
On Thu, Sep 24, 2026 at 09:49:45AM -0400, Sasha Levin wrote:
> Add a top-level AGENTS.md symlink to README, so agents load it on their
> own and follow its pointer to the AI guidelines. This keeps a single
> entry point for every reader, and avoids adding a separate copy of the
> policy that could drift from the RST.
Yeah, I think this is fine. I don't want a separate file just for
Agents: we intentionally designed the README to work for them. That
there are Agents missing it is sad, but okay. And the Agents are already
trained to deal with for-human docs, so that it adds more tokens
shouldn't matter here since it's tiny. (If it reads the contribution
docs before every patch creation that seems like a good thing?)
Acked-by: Kees Cook <kees@kernel.org>
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-09-25 0:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:49 [PATCH] docs: add AGENTS.md as a symlink to README Sasha Levin
2026-09-24 14:31 ` Theodore Tso
2026-09-24 15:18 ` Sasha Levin
2026-09-24 15:08 ` Bradley Morgan
2026-09-24 15:20 ` Sasha Levin
2026-09-24 15:44 ` Bradley Morgan
2026-09-24 16:57 ` Sasha Levin
2026-09-25 0:12 ` Kees Cook [this message]
2026-09-25 7:18 ` Laurent Pinchart
2026-09-26 11:12 ` Antheas Kapenekakis
2026-09-26 15:48 ` Sasha Levin
2026-09-26 17:54 ` Antheas Kapenekakis
2026-09-27 1:13 ` Sasha Levin
2026-09-27 2:42 ` Antheas Kapenekakis
2026-09-27 14:06 ` Sasha Levin
2026-09-27 15:24 ` Antheas Kapenekakis
2026-09-29 14:02 ` Sasha Levin
2026-09-29 15:02 ` Antheas Kapenekakis
2026-09-29 16:10 ` Antheas Kapenekakis
2026-10-07 8:52 ` Sasha Levin
2026-10-07 10:57 ` Antheas Kapenekakis
2026-09-29 16:35 ` Joshua Peisach
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=202609241709.8B710211@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.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 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.