![](https://seccdn.libravatar.org/avatar/ed90d0132a4f59f2d3a1cf82a1b70915.jpg?s=120&d=mm&r=g)
On 09.08.21 20:21, Per Jessen wrote:
Stefan Seyfried wrote:
On 08.08.21 15:34, jdd@dodin.org wrote:
In a doc, there should not be any "context specific" that is not immediately obvious, so you can change it asap.
One example: You document a workaround to get something working (let's say your bluethooth adapter).
As an example, I would suggest my brief amendment of the article on how to read 1-wire devices on an ARM board.
One year later, I come around and find that I do not need your work around to get bluetooth working. But was it fixed over time or is it just that my (slightly different) hardware does not need the workaround yours needs?
When you are so involved anyway, you will probably know, and be able to update the article ?
The easiest way would be to ask the original author of the hint.
He may have no idea about your (slightly different) hardware.
You misunderstood. It is me not having his hardware and wondering if his (old? outdated?) workaround can be removed from the documentation.
Finding this person easily is a good thing.
Which the wiki supports.
How? I have not found a "svn praise" like function that lists the last-changed author for every line. If it is there, then my remaining complaint would be that it's online-only. Anyway. I think I'm out of this discussion (and probably off this list), as my primary goal is improving *my* mood ;-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman