From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>,
workflows@vger.kernel.org, ksummit@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org,
rdunlap@infradead.org, broonie@kernel.org, tytso@mit.edu
Subject: Re: [PATCH 1/2] agents: add infrastructure for agent resources
Date: Fri, 9 Oct 2026 10:22:44 -0400 [thread overview]
Message-ID: <20261009-nebulous-prophetic-caiman-c7842c@lemur> (raw)
In-Reply-To: <asj4FCbBoca8TUK6@laps>
On Fri, Oct 09, 2026 at 10:20:04AM -0400, Sasha Levin wrote:
> > > +AGENT RESOURCES
> > > +M: Sasha Levin <sashal@kernel.org>
> > > +L: linux-kernel@vger.kernel.org
> > > +S: Maintained
> > > +F: agents/
> >
> > If you choose a separate entry instead of adding this to the existing
> > "Documentation Process" entry, let's update the mailing list to
> > workflows@vger.kernel.org. This is where all process changes are announced.
>
> Hm... What do you think Konstantin?
>
> I remember the workflows@ list was originally created to share our
> secret/magical workflows, and I'm not sure that this one qualifies. We can
> start a new list too if it's easier.
Eh. At this point I'm trying to shove everyone towards "just use dfn: queries
for your stuff, stop relying on actual 'lists'". I'd just leave it as
linux-kernel@vger, honestly, since the automated patch churn may annoy those
people on the workflows list that we actually want to keep there.
-K
next prev parent reply other threads:[~2026-10-09 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:54 [PATCH 0/2] agents: add portable agent skills and Fixes attribution Sasha Levin
2026-10-08 22:54 ` [PATCH 1/2] agents: add infrastructure for agent resources Sasha Levin
2026-10-09 10:27 ` Greg KH
2026-10-09 10:35 ` Sasha Levin
2026-10-09 10:53 ` Greg KH
2026-10-09 13:40 ` Leon Romanovsky
2026-10-09 14:20 ` Sasha Levin
2026-10-09 14:22 ` Konstantin Ryabitsev [this message]
2026-10-09 16:36 ` Leon Romanovsky
2026-10-09 22:28 ` Konstantin Ryabitsev
2026-10-08 22:54 ` [PATCH 2/2] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-10 9:40 ` Thorsten Leemhuis
2026-10-10 10:33 ` Michael S. Tsirkin
2026-10-09 9:42 ` [PATCH 0/2] agents: add portable agent skills and Fixes attribution Laurent Pinchart
2026-10-09 10:11 ` Sasha Levin
2026-10-09 16:30 ` Theodore Tso
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=20261009-nebulous-prophetic-caiman-c7842c@lemur \
--to=konstantin@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=leon@kernel.org \
--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=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
all inboxes | Powered by JetHome®