Following the delayed branch of the DBA module as discussed here I'd like to pose a question to Module/CVS maintainers...
Do you really expect contributors to submit functionality changes without any code style repairs, or vice-versa, bother with code style repairs if they are not doing any bugfix or additional functionality?
<X-POST>...
I sympathise with both sides of the story here. :-/
I find it really hard to split my head in three when trying to help fix up a module. In the course of porting, it's hard to resist repairing code style issues where I see them, and usually the only reason I'd be opening up the code in the first place is to actually bugfix or add a feature. This inevitably leads to a three-in-one patch :(
However, even if I did get enough encouragement to go back and try to branch those bits into 3 separate patches ... how does one go about that?
Should random style/text/comment fixes come first? (effectively repairing a release you are not even intending to, or even able to, run - which may be critically broken in the first place - boring)