> What I'd suggest is: import
> enough of kbuild 2.5 to support the feature (in some case nothing
> needs to be imported), then make it work also for old kbuild (in
> some cases that will require no work. This I'd call cooperation,
> which would look good on everybody involved.
Again wrong approah. Extend kbuild-2.4 with the features, tweak them until
they actually meet the requirements and then on to the next step.
Obviously the dependency step is huge, but the point is that there is
steps before and after this.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/