Third in a long series of complaints... See part 1 and part 2 for previous atrocities.

Here's some more simple and easy things that you can do to ensure that you never get your code reviewed for inclusion:

• Send a request for review to a mailing list and only point to a cvs tree on some random sourceforge server for where the changes are at.
• Send a request for review to a mailing list consisting of a single email message with 5 patches composing of over 11 thousand lines of changes (which made up a single 356Kb email message). Said patches were a simple repost of a previous patch written by someone else, yet modified in unknown ways, and 4 other, not properly explained patches.
• When asked to split the previously mentioned patches up into nicer pieces and explain further, respond off-the-list with the answers to the questions, preventing any other people on the mailing list from knowing the answers, or even realizing that anyone responded to the questions.

Yes, this was two different people who did this, but they are all things that these people should know better than to do as the rules on how to do this properly are very well documented.

This post is brought to you today by the letters I, B, and M.

posted Wed, 19 Oct 2005 in [/linux]