Distributed storage release: sik tee or kunem kez.
I asked a friend to translate very common phrase into not very common in kernel communitey at least language, so that I could use it as a name release without insulting too sensitive people. Because this is not just a phrase, but words which clearly describes my feeling about linux kernel review and feedback process. And maybe somewhat about kernel itself.
This is the 10′th renewed DST release and third resend of the same code, I added comments, changed name and turned on and off some debug messages for the previous releases. The last public DST comment was received more than a month ago, and it concerned whitespace placement in the patch. Since than patch was sent 4 times including changed whitespaces and added documentation. And still no feedback. I ask for inclusion, but the first I want to implement a good idea. This can be proved in discussion, and since it does not happen with people directly added into To: list, I get this as there are no objections on the idea and implementation: either because none cares or patch is perfect.
To understand the roots of this issue, I made a simple experiment with the previous DST release. I added following lines into the patch to catch reviewer’s eyes:
+ +ass licker +static char dst_name = "Successful erackliss screwing into"; +
As you may expect, this does not compile and thus was never read by the people who are subscribed to the appropriate mail lists. I got one private mail about this fact for the whole week. The same DST code (without above lines) was sent public first time more than month ago and was resent 3 times after that.
That’s why I do not care about DST inclusion anymore. I do not care about its linux-kernel@ feedback.
I care about project, so if you use it, send mails directly to me and soon-to-be opened DST (there will be lots of mail lists for every project in active state) mail list, and problem will be fixed with the highest priority.