Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, workflows@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] btrfs: add a per-subsystem agent file
Date: Fri, 20 Nov 2026 09:43:39 +0100	[thread overview]
Message-ID: <fdb2526b-2fbf-46f7-b7ad-c4ec0385464e@kernel.org> (raw)
In-Reply-To: <eb62aa0a-b027-4fc7-8d84-05fc5329576c@suse.com>

On 19/11/2026 22:15, Qu Wenruo wrote:
> 
> 
> 在 2026/11/19 20:44, Krzysztof Kozlowski 写道:
>> On 17/11/2026 06:58, Qu Wenruo wrote:
>>> I believe btrfs is not the most affected sub-system, but a lot of
>>> newbies without common senses are doing more harm than help.
>>> E.g. wasting a lot of human review time on very low value fixes, filled
>>> with long paragraphs and useless test steps/results.
>>>
>>> So it would be better to let those agents to stop being stupid and
>>> follow the more common practices here, and hopefully those newbies can
>>> build some common sense.
>>>
>>> I hope the agent file is clear and short enough, that is not only
>>> readable for LLMs, but also for humans who want to be long term
>>> contributers.
>>
>> Then it should be a maintainer profile. We should write docs for humans,
>> which can be used by agents. Not the other way around.
> 
> In that case, what's the proper file that can also be applied to LLM?
> 

I just wrote... why would the LLM skip the most important document for
given subsystem - the maintainer profile? It wouldn't...

Best regards,
Krzysztof

  reply	other threads:[~2026-11-20  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  5:58 [PATCH] btrfs: add a per-subsystem agent file Qu Wenruo
2026-11-17  9:37 ` Leon Romanovsky
2026-11-19 10:14 ` Krzysztof Kozlowski
2026-11-19 21:15   ` Qu Wenruo
2026-11-20  8:43     ` Krzysztof Kozlowski [this message]
2026-11-20  9:14       ` Qu Wenruo

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=fdb2526b-2fbf-46f7-b7ad-c4ec0385464e@kernel.org \
    --to=krzk@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=workflows@vger.kernel.org \
    --cc=wqu@suse.com \
    /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