As a part of my job, I have to try different kernel configuration options until I find the correct set of customized options for our hardware.
So for example, let's say I start with 2.6.29 and I would compile at least 12-15 different kernel based on 2.6.29 with different configuration options (no source code changes). I usually append a string to my image name with --append-to-version=test1 so that I can identify them later.

Then let's say 2.6.30 comes and I take my last build of my 2.6.29 kernel and copy it to 2.6.30 and do make oldconfig and form there I again build different kernels with different config option based on 2.6.30. And this process goes on and on.

However, I am looking for some kind tracking system which would track my different configuration options. I know I can manually diff my config files and see what changes I made to the config options but it is not very convenient. Also I would like to add some changelog before I build a new kernel every time. I am not sure if there is something out there which will suit my requirement. Not sure if using "git" would be overkill since it is mainly used for source code changes and allowing 1000s of people to work together.

I am looking for some sort of my own customize method that I can use for my specific tasks.

Any ideas?

If it's just the config file then you don't need GIT, SVN or CVS as RCS would do just fine. Just gotta have the discipline to make commit notes.

That's what I thought so. But just wanted to get some idea if any one else knows if such a tool exits or is required.

Thank you for your answers.

Hi,

Perhaps you can try this for versioning control?

Personally, I just create and name a directory with the revision number different from the source directory. Then I run against the source directory so that any changes done in the current directory doesn't affect the original source directory. Would that help?

I'm not the OP but RCS at least takes care of that part of "managing stuff" and for instance allows you to add notes so you can "rlog" and read back the changelog...