Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Theodore Tso <tytso@mit.edu>
Cc: workflows@vger.kernel.org, ksummit@lists.linux.dev,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Mark Brown <broonie@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Leon Romanovsky <leon@kernel.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Kees Cook <kees@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Dan Carpenter <error27@gmail.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Julia Lawall <julia.lawall@inria.fr>, SJ Park <sj@kernel.org>,
	Bradley Morgan <brads@mainlining.org>,
	Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH v5 0/6] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages
Date: Thu, 12 Nov 2026 15:56:15 +0100	[thread overview]
Message-ID: <45fd1a88-8fbf-4735-9892-c374d8bf4df5@kernel.org> (raw)
In-Reply-To: <avXOSg4jOlzBY1r5@mit.edu>

On 12/11/2026 15:42, Theodore Tso wrote:
> On Thu, Nov 12, 2026 at 02:49:09PM -0500, Krzysztof Kozlowski wrote:
>>
>> Specification is also documentation, just like for example specification
>> for our ABI. It's also located in Documentation directory.
> 
> Source and header files can also contain documentation.  But we don't
> put them in the Documentation directory because they do not contain
> *exclusively* documentation.

The type of file and its main purpose is a C unit file. Documentation is
only an addon to that.

Here, the main purpose and type of file is documentation. Specification
IS a documentation, just like in-kernel ABI specification is.

I found no other than RST and MD files in this patchset, so I really do
not understand why this is not documentation.

> 
> If the complaint is that it is visible when we run "ls", one

Yes, that's one complain and making it hidden is improving the
perception, but it does not solve the point - it's Documentation so
should be placed in respective directory.

> compromise might be to put the skills in .agents/skills.  This is a
> cross-harness standard which is supported by some code harneses
> (Google Antigravity, Github Copilot, etc.).  Some harneses (including
> Claude Code, Opencode) don't, but people who use these harneses can
> solve it by installing their own symlink from .claude/skills,
> .opencode/skills, etc. to the right place.

Why does it have to be in the top-level in the first place? There is no
point in making LLM stuff visible to humans, except maybe pleasing
people behind upcoming IPO...

Best regards,
Krzysztof

  reply	other threads:[~2026-11-12 14:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 22:59 [PATCH v5 0/6] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages Theodore Ts'o
2026-11-11 22:59 ` [PATCH v5 1/6] agents: add infrastructure for agent resources Theodore Ts'o
2026-11-11 22:59 ` [PATCH v5 2/6] agents: add a skill to determine Fixes tags Theodore Ts'o
2026-11-11 22:59 ` [PATCH v5 3/6] agents: add a skill to determine stable tags Theodore Ts'o
2026-11-12  1:10   ` Andrew Morton
2026-11-12  2:32     ` Sasha Levin
2026-11-12  2:50       ` Andrew Morton
2026-11-12  7:06   ` Miguel Ojeda
2026-11-11 22:59 ` [PATCH v5 4/6] agents: add a skill to find other instances of a fixed bug Theodore Ts'o
2026-11-11 22:59 ` [PATCH v5 5/6] agents: add a skill to write commit messages Theodore Ts'o
2026-11-11 22:59 ` [PATCH v5 6/6] agents: add a skill to write KUnit tests Theodore Ts'o
2026-11-12  0:57   ` Mauro Carvalho Chehab
2026-11-12  1:12   ` Andrew Morton
2026-11-12  8:26 ` [PATCH v5 0/6] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages Krzysztof Kozlowski
2026-11-12 13:46   ` Theodore Tso
2026-11-12 13:49     ` Krzysztof Kozlowski
2026-11-12 14:12       ` Sasha Levin
2026-11-12 14:17         ` Krzysztof Kozlowski
2026-11-12 14:42       ` Theodore Tso
2026-11-12 14:56         ` Krzysztof Kozlowski [this message]
2026-11-12 14:32 ` Sasha Levin

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=45fd1a88-8fbf-4735-9892-c374d8bf4df5@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --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=julia.lawall@inria.fr \
    --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=sashal@kernel.org \
    --cc=sj@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=stable@vger.kernel.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