Jonathan Corbet <cor...@lwn.net> writes:
> Bagas Sanjaya <bagasdo...@gmail.com> writes:
>
>> Atomic types, atomic bitops, and memory barriers docs are included in kernel
>> docs build since commit e40573a43d163a ("docs: put atomic*.txt and
>> memory-barriers.txt into the core-api book") as a wrapper stub for
>> corresponding uncoverted txt docs. Let's turn them into full-fledged reST
>> docs.
>
> Did it occur to you to look at the changelog for the commit you cite,
> which explains why those documents are handled the way they are...?
I'm sorry, that caught me at the wrong time, and I was rather more harsh
than I should have been. I should not have responded that way.
For future reference, though, when somebody has gone out of their way to
accomplish a task in a specific way, there usually *is* a reason for it.
If you can't find that reason, the best thing to do is usually to ask.
Thanks,
jon
