Re: [PATCH] [v3] Documentation: Provide guidelines for tool-generated content
Miguel Ojeda <[email protected]> Fri, 9 Jan 2026 17:30:17 +0100
| Newsgroups | dev.linux.lists.ksummit,org.kernel.vger.linux-kernel,org.kernel.vger.workflows |
|---|---|
| Message-ID | <CANiq72=yOkv_GK=V5k-WTYE-Fv++K+OtVUdrLQcH+75qRMN-Aw@mail.gmail.com> |
On Thu, Jan 8, 2026 at 8:28 PM Lorenzo Stoakes <[email protected]> wrote: > > 'You _can_ be more transparent by adding information like this:...' I am not a native speaker, but my reading of that "can" was that it is suggesting ways to be more transparent that may or may not apply in particular cases, but the requirement of being transparent was already established by the previous sentence: Second, when making a contribution, be transparent about the origin of content in cover letters and changelogs. Which is reinforced by another imperative in the bullet point about prompts: If code was largely generated from a single or short set of prompts, include those prompts. Similarly, I read those other "might"s you quote like a set of things that could happen or not (and is not exhaustive) in particular cases and/or depending on the maintainer etc. At least that is my reading, and as far as I understood the TAB discussions, the goal of this patch was to document that non-trivial tool usage needs to be disclosed, including LLM use, and to me the patch already did that, but perhaps the wording can be more direct. I hope that clarifies a bit... Cheers, Miguel