All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Sasha Levin <sashal@kernel.org>,
	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,
	workflows@vger.kernel.org
Subject: Re: [PATCH 0/2] agents: add portable agent skills and Fixes attribution
Date: Thu, 15 Oct 2026 10:42:50 -0400	[thread overview]
Message-ID: <atDlfUEr-d_sRP7c@mit.edu> (raw)
In-Reply-To: <CANiq72=raWNCedXQW9dSDwxQTE0hfs9ecyGChRPnWqO6DUvbOw@mail.gmail.com>

On Thu, Oct 15, 2026 at 04:05:56PM -0500, Miguel Ojeda wrote:
> 
> I think it would work fine in practice. But it means that we have to
> split every "skill" into two files (and reformat when we may want to
> move details from one to the other), unless I am missing something.
> 
> So if we keep the files rendered and so on (possibly in
> `Documentation/`), and make use of `.rst` features etc., then I think
> it is worth doing it. If not, i.e. if we just use it as a place to
> "dump text", then I think Markdown may be simpler.

I'm a bit confused why people are assuming that we would need to have
copies of the same or similar content in Documentation/ and agents/.
For agents are are *doing* somethiing --- for example, determining the
correct commit for a Fixes: tag is not something I'd think would be relevant for Documentations.

We dould just as easily say that there is a duplication between
src/linux/ext4/scripts/checkpatch.pl and
Documentation/process/submitting-patches.rst.  Which perhaps there is
some, but is it really that big of a deal?

	      	     	       	    - Ted

  reply	other threads:[~2026-10-15 14:44 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
2026-10-15 14:05             ` Miguel Ojeda
2026-10-15 14:42               ` Theodore Tso [this message]
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=atDlfUEr-d_sRP7c@mit.edu \
    --to=tytso@mit.edu \
    --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=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@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.