From: Jonathan Corbet <corbet@lwn.net>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Sasha Levin <sashal@kernel.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
broonie@kernel.org, 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: Thu, 15 Oct 2026 07:57:35 -0600 [thread overview]
Message-ID: <87jynjrrqo.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CANiq72mgS15ZKwd-u1t1xvAaNf3ivpXdUMmVDfmGRyq1OewLvw@mail.gmail.com>
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes:
> On Thu, Oct 15, 2026 at 3:42 PM Sasha Levin <sashal@kernel.org> wrote:
>>
>> Sorry, what I meant to say is that the spec seems to require markdown as it's
>> preferred format. We can experiment with other options, but then the risk is
>> that we'll break some tools.
>
> Ah, got it, thanks! Yeah, at the very least the `SKILL.md` main file
> should most likely be all Markdown inside (and of course the
> filename).
>
> Now, if we go with `agents/` instead of `Documentation/`, then I would
> personally prefer Markdown for the other files in the same folder like
> the `guide.rst`, but that is just my bias, and it has a small
> disadvantage: if we happen to move things between `Doc/` and
> `agents/`, then it is a bit painful to reformat.
For all that we hear about how smart these tools are, are they really
incapable of dealing with two only slightly different markup formats? I
would really hate to bring in a separate format for this stuff...
jon
next prev parent reply other threads:[~2026-10-15 13:57 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
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 [this message]
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=87jynjrrqo.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=broonie@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@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 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.