Hi Folks Some time ago I suggested to not keep complete kernel config files, but base them on a common basic configuration and diff files, so common settings would be kept in a single file only. This has been implemented in the config.cdiff files. I was falsely convinced, that common config settings could be handled easier that way. I _believe_ now I was wrong.
Working extensively on a few config settings lately I was forced all the time to make a detour by generating full kernel config files from the cdiff files just to upgrade to new kernel releases and modify small settings. This appears orthogonal to the original idea of standardizing kernel configs. It also appears that git does not handle the cdiff files nicely and therefore it appears not to be obvious to merge or rebase the branches. It also appears that upgrading kernel releases always requires to generate a full config to be copied to the new kernel and running make oldconfig or olddefconfig, just to be forced to generate a new diff file afterwards. So this also defeats to a certain degree the usefulness of the kernel diff files. I would like to discuss here if it would not be better to drop this feature as at least for me it does not show any potential to make the administration of the kernel config files any easier. I suggest to move back to keep complete kernel config files. cheers ET ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
