[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bee3cea19d9fc1c97b1816f516fdd5283cebc1e1.camel@perches.com>
Date: Sun, 10 Aug 2025 08:44:58 -0700
From: Joe Perches <joe@...ches.com>
To: Sasha Levin <sashal@...nel.org>
Cc: corbet@....net, josh@...htriplett.org, kees@...nel.org,
konstantin@...uxfoundation.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, rostedt@...dmis.org, workflows@...r.kernel.org
Subject: Re: [PATCH v2 1/2] README: restructure with role-based
documentation and guidelines
On Sat, 2025-08-09 at 19:40 -0400, Sasha Levin wrote:
> Reorganize README to provide targeted documentation paths for different
> user roles including developers, researchers, security experts,
> maintainers, and AI coding assistants. Add quick start section and
> essential docs links.
>
> Include proper attribution requirements for AI-assisted contributions
> using Assisted-by tags with agent details and tools used.
Nicely done.
Perhaps the 'Assisted-by:' tag should not be limited to AI
assistance but could also be used when accepted notes were
given on any revised patch submission.
Oh, and maybe a checkpatch update like this?
---
scripts/checkpatch.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index e722dd6fa8ef3..d17661141da79 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -641,6 +641,7 @@ our $signature_tags = qr{(?xi:
Reviewed-by:|
Reported-by:|
Suggested-by:|
+ Assisted-by:|
To:|
Cc:
)};
Powered by blists - more mailing lists