From: Sasha Levin <sashal@kernel.org>
To: Bradley Morgan <brads@mainlining.org>
Cc: broonie@kernel.org, corbet@lwn.net, error27@gmail.com,
geert@linux-m68k.org, gregkh@linuxfoundation.org,
kees@kernel.org, konstantin@linuxfoundation.org,
ksummit@lists.linux.dev, laurent.pinchart@ideasonboard.com,
leon@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@leemhuis.info,
mst@redhat.com, ojeda@kernel.org, rdunlap@infradead.org,
skhan@linuxfoundation.org, tytso@mit.edu,
workflows@vger.kernel.org
Subject: Re: [PATCH v3 1/7] agents: add infrastructure for agent resources
Date: Tue, 20 Oct 2026 09:29:31 -0400 [thread overview]
Message-ID: <20261020132931.3149082-1-sashal@kernel.org> (raw)
In-Reply-To: <348BB89E-AD34-4B22-A7DD-A91E9657D566@mainlining.org>
On Fri, Oct 16, 2026 at 05:02:58PM +0100, Bradley Morgan wrote:
>I feel this "agents" would be ok, make sure not to let it conflict with the
>
>base agents.md file.
They don't overlap: AGENTS.md is the symlink to README that tools look
for, and agents/ holds the skills.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-20 13:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:28 [PATCH v3 0/7] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages Sasha Levin
2026-10-16 15:28 ` [PATCH v3 1/7] agents: add infrastructure for agent resources Sasha Levin
2026-10-16 16:02 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin [this message]
2026-10-16 15:28 ` [PATCH v3 2/7] docs: submitting-patches: say which commit a Fixes tag names Sasha Levin
2026-10-16 16:03 ` Bradley Morgan
2026-10-17 8:07 ` Thorsten Leemhuis
2026-10-20 13:54 ` Sasha Levin
2026-10-20 14:26 ` Thorsten Leemhuis
2026-10-16 15:28 ` [PATCH v3 3/7] docs: stable-kernel-rules: drop rules the stable trees do not apply Sasha Levin
2026-10-16 15:59 ` Greg Kroah-Hartman
2026-10-16 16:01 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin
2026-10-17 16:44 ` SJ Park
2026-10-16 15:28 ` [PATCH v3 4/7] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-16 16:04 ` Bradley Morgan
2026-10-16 15:28 ` [PATCH v3 5/7] agents: add a skill to determine stable tags Sasha Levin
2026-10-16 16:04 ` Bradley Morgan
2026-10-16 15:28 ` [PATCH v3 6/7] agents: add a skill to find other instances of a fixed bug Sasha Levin
2026-10-16 16:05 ` Bradley Morgan
2026-10-16 18:00 ` Julia Lawall
2026-10-16 18:09 ` Sasha Levin
2026-10-16 18:17 ` Julia Lawall
2026-10-16 18:32 ` Sasha Levin
2026-10-16 15:28 ` [PATCH v3 7/7] agents: add a skill to write commit messages Sasha Levin
2026-10-16 16:05 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin
2026-10-16 16:00 ` [PATCH v3 0/7] agents: add skills for Fixes tags, stable tags, similar bugs, and " Miguel Ojeda
2026-10-20 13:31 ` Sasha Levin
2026-10-20 16:23 ` Miguel Ojeda
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=20261020132931.3149082-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=brads@mainlining.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=error27@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mst@redhat.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--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