From: Miguel Ojeda <ojeda@kernel.org>
To: sashal@kernel.org
Cc: broonie@kernel.org, corbet@lwn.net, ksummit@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, skhan@linuxfoundation.org, tytso@mit.edu,
workflows@vger.kernel.org
Subject: Re: [PATCH 0/2] agents: add portable agent skills and Fixes attribution
Date: Wed, 14 Oct 2026 19:48:38 +0200 [thread overview]
Message-ID: <20261014174838.114990-1-ojeda@kernel.org> (raw)
In-Reply-To: <cover.1791499378.git.sashal@kernel.org>
On Thu, 08 Oct 2026 18:54:51 -0400 Sasha Levin <sashal@kernel.org> wrote:
>
> I'm not sure whether this belongs under Documentation/ or in a separate
> agents/ directory at the root. I'm open to changing the location.
Either way, we still need local setup to use these skills in at least a couple
popular tools, right?
One discussion point could be which markup language to use. If we were to do it
in `agents/`, I guess Markdown could be a possibility. But reStructuredText and
having it in `Documentation/` would allow to have it rendered and to "link"
things more easily, which could potentially be useful for certain skills.
Anyway, I tested it with a simple case invoking it explicitly, and it seems to
work, including one where it was not an actual bug (it complained about it :).
Cheers,
Miguel
next prev parent reply other threads:[~2026-10-14 17:49 UTC|newest]
Thread overview: 30+ 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
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-10 13:45 ` Sasha Levin
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
2026-10-14 17:48 ` Miguel Ojeda [this message]
2026-10-14 17:58 ` Sasha Levin
2026-10-14 20:28 ` Theodore Tso
2026-10-14 21:39 ` Miguel Ojeda
2026-10-14 21:37 ` Miguel Ojeda
2026-10-15 13:42 ` Sasha Levin
2026-10-15 13:51 ` Miguel Ojeda
2026-10-15 13:57 ` Jonathan Corbet
2026-10-15 14:05 ` Miguel Ojeda
2026-10-15 14:42 ` Theodore Tso
2026-10-15 16:15 ` Miguel Ojeda
2026-10-15 14:47 ` Sasha Levin
2026-10-15 15:34 ` Jonathan Corbet
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=20261014174838.114990-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--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