Hi KP Am 14.04.2015 um 17:32 schrieb kp kirchdoerfer: > HI Erich; ...
> > > This is all correct; and I may have disturbed it. > I confess I never got used to the idea and when I ran into pb's it was the > short path to adjust the config files. > Once we move to a newer kernel, we, and esp. myself, should take care to get > it right. Any help is welcome. > For the current version we may have to live with the faults I've made. Not a question of fault or anything, I am just trying to understand the way the config files get updated. My idea was 1) take the current base config to the new kernel and run make olddefconfig to get the new options with the their defaults inserted, save the base config to Bering-n.nn.nn.config 2) do the same with all the variants 3) diff the variant config to the saved base config to build the patches. Just save the base config and the patches to git. There is no need for the variant configs as they get created using the patch files. Common settings for all the variants should only go into the base config file. This would result in small and simple patches. I am trying to build a version of the base config with all the common settings in a separate branch and see of I can come up with identical results. cheers ET
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
