Thank you.
I am sorry, that your SVN client choked upon one patch. I will try to use svn diff instead. I still choke on the description in the cb wiki.
When looking at the bug tracker, my gut feeling is, that, although issues are not lost, they accumulate and many are still not dealt with. Tthis is not surprising.
Even, when an issue is a real one, often it may be hard to reproduce and fix -- and not to break something else unnoticed.
Especially, when there are no tests and the code has changed since the bug entry had been added. In the worst case, the "blast radius" of a bug might be huge when the separation of concerns is suboptimal.
If the code has evolved from a state a patch relies upon, it actually might be preferable to let the patch get lost in a black hole.
Granted, "issues" like the patches I provided are a piece of cake compared to the majority of listed issues. So they have a slightly higher chance of beeing dealt with/applied in the very near future. But even that might increases the effort a bit and feedback time a lot. That in turn erodes motivation.
If people observe obscure or rare bugs, my motivation to spend an unknown amount of time for bug-hunting is fairly limited when at the same time, several static/dynamic analysis tools like compiler warnings, cppcheck, sanitizer or clang-tidy already point out numerous potential (albeit not confirmed) issues. In that case, I prefer to deal with the low hanging fruit first.
When, like cb, the code depends on volunteers to help out, every single obstacle someone stumbles across, reduces the ability and motivation to help significantly.
Thanks again for applying the patches.
Have a nice day.