From: Qu Wenruo <wqu@suse.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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 07:45:35 +1030 [thread overview]
Message-ID: <eb62aa0a-b027-4fc7-8d84-05fc5329576c@suse.com> (raw)
In-Reply-To: <63566373-86cc-4a55-8e09-741f283e6786@kernel.org>
在 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?
Thanks,
Qu
>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2026-11-19 21:15 UTC|newest]
Thread overview: 4+ 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 [this message]
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=eb62aa0a-b027-4fc7-8d84-05fc5329576c@suse.com \
--to=wqu@suse.com \
--cc=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 \
/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