docs: netdev: suggest that it's okay to rewrite AI generated patches
Subsystems (4)
Jakub Kicinski
maintainerRFC 1/1 docs: netdev: suggest that it's okay to rewrite AI generated patches
This has been on my mind. Not sure if anyone actually has the cycles to rewrite patches, but I'm slightly worried that maintainers may feel frustrated when dealing with people who just feed their review to an LLM. Should we make it clear that it's okay to take over? Or is this already obvious to everyone?
Signed-off-by Jakub Kicinski <[email protected]>
--- Documentation/process/maintainer-netdev.rst | 10 ++++++++++ 1 file changed, 10 insertions(+)
Documentation/process/maintainer-netdev.rst +10 -0
@@ -311,6 +311,16 @@ OK with that, then perhaps consider mailing [email protected] or reading about http://oss-security.openwall.org/wiki/mailing-lists/distros as possible alternative mechanisms. +AI-generated fixes +~~~~~~~~~~~~~~~~~~ + +AI-generated fixes should carry the ``Assisted-by:`` tag. + +Maintainers should treat AI-generated fixes as equivalent to a bug report. +Taking over and submitting an alternative fix is normally frowned upon. +It is okay to do so for AI-generated fixes, however, if the posted patch +is far from the desired implementation. The original reporter must be +acknowledged with a ``Reported-by:`` tag in those cases. Co-posting changes to user space components ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Signature · 1 line
2.54.0