On Thu, Oct 15, 2026 at 04:05:56PM -0500, Miguel Ojeda wrote:
>
> I think it would work fine in practice. But it means that we have to
> split every "skill" into two files (and reformat when we may want to
> move details from one to the other), unless I am missing something.
>
> So if we keep the files rendered and so on (possibly in
> `Documentation/`), and make use of `.rst` features etc., then I think
> it is worth doing it. If not, i.e. if we just use it as a place to
> "dump text", then I think Markdown may be simpler.
I'm a bit confused why people are assuming that we would need to have
copies of the same or similar content in Documentation/ and agents/.
For agents are are *doing* somethiing --- for example, determining the
correct commit for a Fixes: tag is not something I'd think would be relevant
for Documentations.
We dould just as easily say that there is a duplication between
src/linux/ext4/scripts/checkpatch.pl and
Documentation/process/submitting-patches.rst. Which perhaps there is
some, but is it really that big of a deal?
- Ted
