> Clearly not, as nobody in their sane mind writes C code as a set on one-line files to be #included.
what does a sane mind have to do with the GPL and its 'preferred form for modification' clause? as the creator of a derived work, i can pretty much do 'whatever' i want to the 'source code'. say, i can split up all the files into one-liners, or i can go the other way as well, it's all within my rights to change the 'source code' any way i want (obviously i can't remove the GPL itself or anything else the GPL says). what we're talking about here is the form this changed work has to be distributed in. you (well, tomcatsdb) said that original sources + patches were not mandated by the GPL because (in his reading) the only requirement of the GPL here is the ability to build the distributed binary. my example derived work satisfies that criterion. if it doesn't, then you'll have to change your reading of this GPL clause. so which is it? ;)